On 03/11/2017 09:42 AM, Krzysztof Kozlowski wrote:
Simplify the flow in helper function for getting the driver data by
using of_device_get_match_data() and only one if() branch.
The code should be equivalent.
Signed-off-by: Krzysztof Kozlowski
---
drivers/watchdog/s3c2410_wdt.c | 17 +
On 03/11/2017 09:42 AM, Krzysztof Kozlowski wrote:
Cleanup the code from minor readability issues (no functional changes):
1. Fix checkpatch: ERROR: Do not include the paragraph about writing to
the Free Software Foundation's mailing address.
2. Fix checkpatch: WARNING: quoted string split acr
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/usb/catc.c | 31 ++-
1 files
On Sun, Mar 12, 2017 at 08:40:37PM +, Russell King - ARM Linux wrote:
> On Sun, Mar 12, 2017 at 01:36:32PM -0700, Steve Longerbeam wrote:
> > But hold on, if my logic is correct, then why did the CSI power-off
> > get reached in your case, multiple times? Yes I think there is a bug,
> > link_no
On Sun, Mar 12, 2017 at 05:59:28PM -0300, Mauro Carvalho Chehab wrote:
> Yet, udev/systemd has some rules that provide an unique name for V4L
> devices at /lib/udev/rules.d/60-persistent-v4l.rules. Basically, it
> runs a small application (v4l_id) with creates a persistent symling
> using rules lik
On Sun, Mar 12, 2017 at 02:01:32AM +0200, Michael S. Tsirkin wrote:
> On Fri, Mar 10, 2017 at 03:46:45PM -0800, Jim Mattson wrote:
> > On Thu, Mar 9, 2017 at 2:29 PM, Michael S. Tsirkin wrote:
> > > Some guests call mwait without checking the cpu flags. We currently
> >
> > "Some guests"? What g
On Sun, 12 Mar 2017, Samuel Thibault wrote:
> Some USB 2.0 devices erroneously report millisecond values in
> bInterval. The generic config code manages to catch most of them,
> but in some cases it's not completely enough.
>
> The case at stake here is a USB 2.0 braille device, which wants to
>
On Sat 2017-03-11 23:14:56, Russell King - ARM Linux wrote:
> On Sat, Mar 11, 2017 at 08:25:49AM -0300, Mauro Carvalho Chehab wrote:
> > This situation is there since 2009. If I remember well, you tried to write
> > such generic plugin in the past, but never finished it, apparently because
> > it i
Hi Arushi,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.11-rc1 next-20170310]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Arushi-Singhal/staging-sm750fb-Imp
On Thu, Mar 09, 2017 at 03:26:02PM -0800, Linus Torvalds wrote:
> Maybe it's the lguest games with PGE that need to be removed?
Btw, tglx suggested something else the other day: warn when we're
changing boot_cpu_data x86_capability bits *after* alternatives have
run. The reasoning behind it being
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/usb/r8152.c | 21 -
1 files changed,
Alan Stern, on dim. 12 mars 2017 17:18:51 -0400, wrote:
> Interesting. This is a high-speed device that mistakenly uses the
> low/full-speed encoding for an interrupt bInterval value?
Yes...
> That's pretty unusual. Most HID devices (which includes the Braille
> devices I have heard of) run at
Some USB 2.0 devices erroneously report millisecond values in
bInterval. The generic config code manages to catch most of them,
but in some cases it's not completely enough.
The case at stake here is a USB 2.0 braille device, which wants to
announce 10ms and thus sets bInterval to 10, but with the
[quoted lines by Alan Stern on 2017/03/12 at 17:18 -0400]
>Interesting. This is a high-speed device that mistakenly uses the
>low/full-speed encoding for an interrupt bInterval value?
Yes.
>That's pretty unusual. Most HID devices (which includes the Braille
>devices I have heard of) run at lo
On Mon, Mar 13, 2017 at 06:11:12AM +1000, Dave Airlie wrote:
> On 13 March 2017 at 05:44, Greg KH wrote:
> > Hi Daniel and Jani and other members of the i915-commit-cabal,
> >
> > I've mentioned this a few times to Daniel in the past (like at the last
> > kernel summit), but the way you all are ha
On Sat, Mar 11 2017, Jens Axboe wrote:
> On 03/09/2017 11:00 PM, NeilBrown wrote:
>> This is a rebase of the series I sent earlier, based on the
>> very latest from Linus, which included my first patch.
>>
>> The first fixes a problem that patch introduced, and so should go to
>> Linux promptly.
Em Sun, 12 Mar 2017 10:56:53 -0700
Steve Longerbeam escreveu:
> On 03/11/2017 11:37 PM, Russell King - ARM Linux wrote:
> > On Sat, Mar 11, 2017 at 07:31:18PM -0800, Steve Longerbeam wrote:
> > Given what Mauro has said, I'm convinced that the media controller stuff
> > is a complete failure f
__USE_MISC is glibc specific and not available in musl libc. Only do
this check when glibc is used. This fixes a problem with musl libc.
Signed-off-by: Hauke Mehrtens
---
include/uapi/linux/libc-compat.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/l
Instead of checking if this header file is used in the glibc, check if
iti is not used in kernel context, this way it will also work with
other libc implementations like musl.
Signed-off-by: Hauke Mehrtens
---
include/uapi/linux/libc-compat.h | 8
1 file changed, 4 insertions(+), 4 dele
musl 1.1.15 defines IFF_ECHO and the other net_device_flags options.
When a user application includes linux/if.h and net/if.h the compile
will fail.
Activate __UAPI_DEF_IF_NET_DEVICE_FLAGS_LOWER_UP_DORMANT_ECHO only when
it is needed. This should also make this work in case glibc will add
these de
The code from libc-compat.h depends on some glibc specific defines and
causes compile problems with the musl libc. These patches remove some
of the glibc dependencies. With these patches the LEDE (OpenWrt) base
user space applications can be build with unmodified kernel headers and
musl libc.
As usual, the week after rc1 tends to be fairly quiet when people are
still looking for bugs and taking a breather after the merge window.
But we've got a healthy number of fixes in, and there's some
cleanup/prep patches for the upcoming 5-level page table support that
I took after the merge window
This patch fixes the following sparse warnings:
drivers/staging/rtl8192u/r8192U_dm.c:2307:49: warning: cast from restricted
__le16
drivers/staging/rtl8192u/r8192U_dm.c:2308:44: warning: cast from restricted
__le16
drivers/staging/rtl8192u/r8192U_dm.c:2309:44: warning: cast from restricted
__le16
From: David Heidelberger
Musl provides its own ethhdr struct definition. Add a guard to prevent
its definition of the appropriate musl header has already been included.
Signed-off-by: John Spencer
Tested-by: David Heidelberger
Signed-off-by: Jonas Gorski
---
include/uapi/linux/if_ether.h
On Sun, Mar 12, 2017 at 09:46:21PM +0100, Daniel Vetter wrote:
> On Sun, Mar 12, 2017 at 08:44:40PM +0100, Greg KH wrote:
> > Hi Daniel and Jani and other members of the i915-commit-cabal,
> >
> > I've mentioned this a few times to Daniel in the past (like at the last
> > kernel summit), but the w
Em Sun, 12 Mar 2017 21:13:24 +
Russell King - ARM Linux escreveu:
> On Sun, Mar 12, 2017 at 05:59:28PM -0300, Mauro Carvalho Chehab wrote:
> > Yet, udev/systemd has some rules that provide an unique name for V4L
> > devices at /lib/udev/rules.d/60-persistent-v4l.rules. Basically, it
> > runs
Hi Radoslaw,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.11-rc2 next-20170310]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Radoslaw-Pietrzyk/staging-fb
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/usb/rtl8150.c | 35 ---
1
On Sun, Mar 12, 2017 at 03:55:08PM +0200, Andy Shevchenko wrote:
> On Sun, Mar 12, 2017 at 2:26 PM, Borislav Petkov wrote:
> > On Sun, Mar 12, 2017 at 12:57:03PM +0100, Borislav Petkov wrote:
> >> On Sat, Mar 11, 2017 at 09:37:23PM -0800, l...@pengaru.com wrote:
> >> > Hello list,
> >> >
> >> > He
On 02/14/2017 12:34 PM, Eddie James wrote:
From: "Edward A. James"
Add a generic mechanism to expose the sensors provided by the OCC in
sysfs.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ | 62 +++
drivers/hwmon/occ/Makefile|
Em Sun, 12 Mar 2017 22:29:04 +0100
Pavel Machek escreveu:
> Mid-layer is difficult... there are _hundreds_ of possible
> pipeline setups. If it should live in kernel or in userspace is a
> question... but I don't think having it in kernel helps in any way.
Mid-layer is difficult, because we eith
> On Mar 12, 2017, at 4:02 PM, Jonathan Cameron wrote:
>
>> On 05/03/17 15:29, Jason Kridner wrote:
>>
>>
On Mar 5, 2017, at 5:11 AM, Jonathan Cameron wrote:
On 25/02/17 21:12, Jason Kridner wrote:
>> On Feb 19, 2017, at 10:08 AM, Jonathan Cameron wrote:
On 03/12/2017 07:15 PM, Hauke Mehrtens wrote:
> arch/mips/include/asm/processor.h references task_stack_page, but it is
> not defined anywhere. Including linux/sched/task_stack.h directly in
> asm/processor.h caused a different compile warning.
>
> This fixes the folowing compile error in kernel 4
On 03/09/2017 05:30 AM, Shilpasri G Bhat wrote:
Hi Guenter,
On 03/09/2017 05:40 PM, Guenter Roeck wrote:
On Thu, Mar 09, 2017 at 05:19:15PM +0530, Shilpasri G Bhat wrote:
Add support to read power and temperature sensors from OCC inband
sensors which are copied to main memory by OCC.
Is thi
Hi Vivek,
On 03/12/2017 06:18 PM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Thu, Mar 9, 2017 at 5:26 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Thursday 09 March 2017 05:03 PM, Jaehoon Chung wrote:
>>> Make the "samsung" directory and move the Samsung specific files to
>>> there for main
Hi Linus,
I intended to get this to you earlier. Between the job change (Intel to VMware),
rebuilding my CI machine and moving the office, I didn't get it out as soon as I
would have liked. The changes are all very well contained. The fujitsu cleanup
has been in next and ready for a while and I th
try_to_unmap returns SWAP_SUCCESS or SWAP_FAIL so it's suitable for
boolean return. This patch changes it.
Cc: "Kirill A. Shutemov"
Cc: Naoya Horiguchi
Signed-off-by: Minchan Kim
---
include/linux/rmap.h | 4 ++--
mm/huge_memory.c | 6 +++---
mm/memory-failure.c | 26 ---
Currently, try_to_unmap returns various return value(SWAP_SUCCESS,
SWAP_FAIL, SWAP_AGAIN, SWAP_DIRTY and SWAP_MLOCK). When I look into
that, it's unncessary complicated so this patch aims for cleaning
it up. Change ttu to boolean function so we can remove SWAP_AGAIN,
SWAP_DIRTY, SWAP_MLOCK.
* from
try_to_munlock returns SWAP_MLOCK if the one of VMAs mapped
the page has VM_LOCKED flag. In that time, VM set PG_mlocked to
the page if the page is not pte-mapped THP which cannot be
mlocked, either.
With that, __munlock_isolated_page can use PageMlocked to check
whether try_to_munlock is successf
If the page is mapped and rescue in try_to_unmap_one,
page_mapcount(page) == 0 cannot be true so page_mapcount check
in try_to_unmap is enough to return SWAP_SUCCESS.
IOW, SWAP_MLOCK check is redundant so remove it.
Signed-off-by: Minchan Kim
---
mm/rmap.c | 2 +-
1 file changed, 1 insertion(+),
There is no user for it. Remove it.
Signed-off-by: Minchan Kim
---
include/linux/rmap.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/include/linux/rmap.h b/include/linux/rmap.h
index 59d7dd7..5d6788f 100644
--- a/include/linux/rmap.h
+++ b/include/linux/rmap.h
@@ -291,11 +291,4 @@ s
Anyone doesn't use ret variable. Remove it.
Acked-by: Kirill A. Shutemov
Signed-off-by: Minchan Kim
---
mm/rmap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/rmap.c b/mm/rmap.c
index 7d24bb9..9dbfa6f 100644
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -807,7 +807,6 @@ int pag
If we found lazyfree page is dirty, try_to_unmap_one can just
SetPageSwapBakced in there like PG_mlocked page and just return
with SWAP_FAIL which is very natural because the page is not
swappable right now so that vmscan can activate it.
There is no point to introduce new return value SWAP_DIRTY
i
ttu don't need to return SWAP_MLOCK. Instead, just return SWAP_FAIL
because it means the page is not-swappable so it should move to
another LRU list(active or unevictable). putback friends will
move it to right list depending on the page's LRU flag.
Signed-off-by: Minchan Kim
---
include/linux/r
rmap_one's return value controls whether rmap_work should contine to
scan other ptes or not so it's target for changing to boolean.
Return true if the scan should be continued. Otherwise, return false
to stop the scanning.
This patch makes rmap_one's return value to boolean.
Signed-off-by: Mincha
There is no user of return value from rmap_walk friend so this
patch makes them void function.
Signed-off-by: Minchan Kim
---
include/linux/ksm.h | 5 ++---
include/linux/rmap.h | 4 ++--
mm/ksm.c | 16 ++--
mm/rmap.c| 32 +---
4
In 2002, [1] introduced SWAP_AGAIN.
At that time, try_to_unmap_one used spin_trylock(&mm->page_table_lock)
so it's really easy to contend and fail to hold a lock so SWAP_AGAIN
to keep LRU status makes sense.
However, now we changed it to mutex-based lock and be able to block
without skip pte so th
Hi David,
On Sun, Mar 12, 2017 at 09:11:53AM +, David Howells wrote:
> Eric Biggers wrote:
>
> > +static int cp_statx(const struct kstat *stat, struct statx __user *buffer)
> > ...
> > + struct statx tmp;
>
> This function needs to be "noinline" as tmp is big.
>
> > - return statx_set_
Hi,
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Friday, March 10, 2017 6:52 PM
> To: Jun Li
> Cc: NeilBrown ; Felipe Balbi ; Greg KH
> ; Sebastian Reichel ; Dmitry
> Eremin-Solenikov ; David Woodhouse
> ; r...@kernel.org; Marek Szyprowski
> ; Ruslan Bi
Em Sun, 12 Mar 2017 14:16:56 +0100
Geert Uytterhoeven escreveu:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Reviewed-by: Javier Martinez Canillas
> Cc: Mauro Carvalho Chehab
As the T
On Sun, 12 Mar 2017, Samuel Thibault wrote:
> Some USB 2.0 devices erroneously report millisecond values in
> bInterval. The generic config code manages to catch most of them,
> but in some cases it's not completely enough.
>
> The case at stake here is a USB 2.0 braille device, which wants to
>
On Sun, 12 Mar 2017, Dave Mielke wrote:
> [quoted lines by Alan Stern on 2017/03/12 at 17:18 -0400]
>
> >Interesting. This is a high-speed device that mistakenly uses the
> >low/full-speed encoding for an interrupt bInterval value?
>
> Yes.
>
> >That's pretty unusual. Most HID devices (which
I can test it tomorrow. I'll pull a clean copy of 4.10.2, or do you
suggest a different version than that?
Chris
On 2017-03-12 11:02 AM, Philippe Reynes wrote:
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the ha
On Sun, 12 Mar 2017, Dave Mielke wrote:
> [quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400]
>
> >A device's speed is only partially related to its USB version. A
> >USB-1.1 device can run at low speed or full speed. A USB-2 device can
> >run at low, full, or high speed. And a USB-3 dev
Greetings,
This is an old bug and cannot be bisected to its root cause.
Perhaps it requires some manual investigation. The attached
reproduce-* may help the debugging.
efdb4167e6 scripts/faddr2line: Fix "size mismatch" error
bb5e5ce545 x86/dumpstack: Remove kernel text addresses from stack dump
On a Broadcom BCM91250a MIPS system I can reliably trigger NFS
corruption on the first file read.
To demonstrate, I downloaded five identical copies of the gcc-5.4.0
source tarball. On the NFS server, they hash to the same value:
server distfiles # md5sum gcc-5.4.0.tar.bz2*
4c626ac2a83ef30dfb9260
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400]
>No, I was wondering why an HID device would run at high speed. Both
>you and Samuel implied that this was because it was a USB-2 device.
>But that is not an adequate answer, because it is perfectly valid for a
>USB-2 device to run at f
[quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400]
>A device's speed is only partially related to its USB version. A
>USB-1.1 device can run at low speed or full speed. A USB-2 device can
>run at low, full, or high speed. And a USB-3 device can run at low,
>full, high, or Super speed.
Y
Are there nominations for most comprehensive changelog of the year? :)
This is awesome.
-Kees
On Fri, Mar 10, 2017 at 6:31 PM, Daniel Borkmann wrote:
> Fengguang reported [1] random corruptions from various locations on
> x86-32 after commits d2852a224050 ("arch: add ARCH_HAS_SET_MEMORY
> config
On 3/9/2017 19:50, Colin Ian King wrote:
On 09/03/17 11:49, walter harms wrote:
Am 09.03.2017 11:57, schrieb Hans Verkuil:
Hi Songjun,
On 08/03/17 03:25, Wu, Songjun wrote:
Hi Colin,
Thank you for your comment.
It is a bug, will be fixed in the next patch.
Do you mean that you will pro
The patch update the _CRS of LPC children based on the relevant LIBIO
interfaces. Then the ACPI platform device enumeration for LPC can apply the
right I/O resource to request the system I/O space from ioport_resource and
ensure the LPC peripherals work well.
Signed-off-by: zhichang.yuan
Signed-o
This patchset supports the IPMI-bt device attached to the Low-Pin-Count
interface implemented on Hisilicon Hip06/Hip07 SoC.
---
| LPC host|
| |
---
|
The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
I/O port addresses. This patch implements the LPC host controller driver which
perform the I/O operations on the underlying hardware.
We don't want to touch those existing peripherals' driver, such as ipmi-bt. So
this drive
For those hosts which access I/O based on the host/bus local I/O addresses,
their I/O range must be registered and translated as unique logical PIO before
the ACPI enumeration on the devices under the hosts. Otherwise, there is no
available I/O resources allocated for those devices.
This patch impl
After introducing the new generic I/O space management(LIBIO), the original PCI
MMIO relevant helpers need to be updated based on the new interfaces defined in
LIBIO.
This patch adapts the corresponding code to match the changes introduced by
LIBIO.
Signed-off-by: zhichang.yuan
Signed-off-by: Gab
There are some special ISA/LPC devices that work on a specific I/O range where
it is not correct to specify a 'ranges' property in DTS parent node as cpu
addresses translated from DTS node are only for memory space on some
architectures, such as Arm64. Without the parent 'ranges' property, current
Hi, Vlastimil,
On 2017/3/8 15:07, Vlastimil Babka wrote:
> On 03/08/2017 03:16 AM, Yisheng Xie wrote:
>> Hi Vlastimil ,
>>
>> On 2017/2/11 1:23, Vlastimil Babka wrote:
>>> @@ -1977,7 +1978,7 @@ static void steal_suitable_fallback(struct zone
>>> *zone, struct page *page,
>>> unsigned int curr
In commit 40e7fcb1929(ACPI: Add _DEP support to fix battery issue on Asus
T100TA), the '_DEP' was supported to solve the dependency of Asus battery. But
this patch is specific to Asus battery device.
In the real world, there are other devices which need the dependency to play the
role on the enumer
In commit 41f8bba7f55(of/pci: Add pci_register_io_range() and
pci_pio_to_address()), a new I/O space management was supported. With that
driver, the I/O ranges configured for PCI/PCIE hosts on some architectures can
be mapped to logical PIO, converted easily between CPU address and the
correspondin
On 2017/3/11 3:40, Brian Norris wrote:
On Fri, Mar 10, 2017 at 12:20:54PM +0800, Shawn Lin wrote:
On 2017/3/10 11:22, Shawn Lin wrote:
On 2017/3/10 10:46, Brian Norris wrote:
Currently, if we try to unbind the platform device, the remove will
succeed, but the removal won't undo most of the reg
From: Philippe Reynes
Date: Mon, 6 Mar 2017 23:26:09 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Wed, 8 Mar 2017 23:41:04 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
Hi Baicar Tyler,
On 2017/3/11 2:23, Baicar, Tyler wrote:
> Hello Xie XiuQi,
>
>
> On 3/9/2017 2:41 AM, Xie XiuQi wrote:
>> On 2017/3/7 4:45, Tyler Baicar wrote:
>>> Currently there are trace events for the various RAS
>>> errors with the exception of ARM processor type errors.
>>> Add a new trac
From: Philippe Reynes
Date: Wed, 8 Mar 2017 23:16:11 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Wed, 8 Mar 2017 22:20:20 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Tue, 7 Mar 2017 23:46:16 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Tue, 7 Mar 2017 23:32:25 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
I've had no issues building the 4.11.0-rc1+ kernels on x86_64 until some
commits in the last 24 hours, that resulted in:
[ 18.746569] BUG: Bad page map in process libinput-device
pte:3f90 pmd:22
0910067
[ 18.746757] addr:7efd31d0 vm_flags:0870 anon_vma:
(null)
mapping:f
Hi Web User, Your mailbox has
exceeded its mail-quota and due for upgrade.
You can upgrade to extra 5GB web-mail plan now. Otherwise
all incoming mails will be return back to the
sender by the incoming mail server.
Upgrade your Mailbox Now by clicking this link http://formcrafts.com/a/25389
> -Original Message-
> From: Srinivas Kandagatla [mailto:srinivas.kandaga...@linaro.org]
> Sent: Friday, March 03, 2017 6:12 PM
> To: Peng Fan ; shawn...@kernel.org;
> maxime.rip...@free-electrons.com
> Cc: devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> ker...@list
From: K. Y. Srinivasan
When we close a channel that has been rescinded, we will leak memory since
vmbus_teardown_gpadl() returns an error. Fix this so that we can properly
cleanup the memory allocated to the ring buffers.
Fixes: ccb61f8a99e6 ("Drivers: hv: vmbus: Fix a rescind handling bug")
Si
On Sat, Mar 11, 2017 at 6:13 PM, Al Viro wrote:
> PS: AFAICS, simple mount --bind of your pid-only mount will suddenly
> expose the full thing. And as for the lifetimes making no sense...
> note that you are simply not freeing these structures of yours.
> Try to handle that and you'll get a serio
On 10/03/17 08:46 PM, Ben Hutchings wrote:
> 3.16.42-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Michel Dänzer
>
> commit d74c67dd7800fc7aae381f272875c337f268806c upstream.
>
> The crtc_h/vdisplay fields may not match the CRTC viewport
Hi Brian
Thank you for your feedback
> There are 4 drivers calling that:
>
> snd_soc_dummy_probe
> rt5514_spi_probe
> 2 instances of snd_dmaengine_pcm_register, via rockchip_i2s_probe
>
> Only the latter two seem to run the assignment here:
>
> if (platform_drv->pcm_new)
>
On Mon, Mar 13, 2017 at 12:03 AM, Alison Schofield wrote:
> On Sun, Mar 12, 2017 at 07:02:50PM +0530, simran singhal wrote:
>> The IIO subsystem is redefining iio_dev->mlock to be used by
>> the IIO core only for protecting device operating mode changes.
>> ie. Changes between INDIO_DIRECT_MODE, I
The last caller to gup_pud_range was removed in commit c2febafc6773
("mm: convert generic code to 5-level paging"). Mark it as unused to
silence a warning from gcc.
Signed-off-by: Chris Packham
---
I saw this warning when compiling 4.11-rc2 with -Werror. An equally valid fix
would be to remove th
On Sun, Mar 12, 2017 at 10:42 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Fix the debugfs interface for PID tuning to actually update
> pid_params.sample_rate_ns on PID parameters updates, as changing
> pid_params.sample_rate_ms via debugfs has no effect now.
>
> Fixes: a4675fbc4a7
On 03/12/2017 01:22 PM, Russell King - ARM Linux wrote:
On Sun, Mar 12, 2017 at 01:05:06PM -0700, Steve Longerbeam wrote:
On 03/12/2017 12:57 PM, Russell King - ARM Linux wrote:
On Sat, Mar 11, 2017 at 04:30:53PM -0800, Steve Longerbeam wrote:
If it's too difficult to get the imx219 csi-2
On Mar 11, 2017, at 11:01 PM, Eric Biggers wrote:
>
> On Sat, Mar 11, 2017 at 08:02:06PM -0800, Eric Biggers wrote:
>> On Sun, Mar 12, 2017 at 02:29:27AM +, Al Viro wrote:
>>>
>>> Oh, I agree that multiple __put_user() are wrong; I also agree that bulk
>>> copy is the right approach (when we
when percpu devices set its IRQ trigger type using irq_of_parse
and_map API,it will be failed because irq_set_irq_type is only
for 1-N mode interrupt source,not for per-cpu interrupt source.
so handle per-cpu IRQs for this failure.
problem: per cpu device call irq_of_parse_and_map to set its
timer
Hi,
On 2017년 03월 12일 04:01, Krzysztof Kozlowski wrote:
> Static struct regulator_ops is not modified so can be made const for
> code safeness.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/regulator/max77693-regulator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
Hi,
On 2017년 03월 11일 05:52, Hans de Goede wrote:
> Now that we've an acpi mapping table we should be using gpiod_get
> instead of gpiod_get_index.
>
> Cc: Andy Shevchenko
> Signed-off-by: Hans de Goede
> ---
> drivers/extcon/extcon-intel-int3496.c | 12 +++-
> 1 file changed, 3 inserti
On 03/01/2017 05:14 AM, lepton wrote:
> If checking some calling side, the len is from cache_size of struct
> mtdblk_dev, it's defined as unsigned int now. So it's not 64bit yet.
Ummm ... since you're top-posting, I have no clue which part do you
refer to , sorry.
> BTW, seems it's just block si
Dear all,
All patches in this series looks good to me.
Reviewed-by: Chanwoo Choi
Best Regards,
Chanwoo Choi
On 2017년 03월 12일 04:01, Krzysztof Kozlowski wrote:
> Static struct regulator_ops is not modified so can be made const for
> code safeness.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
>
Hi Matthew,
On Sat, Mar 11, 2017 at 06:56:40AM -0800, Matthew Wilcox wrote:
> On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote:
> > +static inline void zram_fill_page(char *ptr, unsigned long len,
> > + unsigned long value)
> > +{
> > + int i;
> > +
On Mon, Mar 13, 2017 at 04:58:37PM +1300, Chris Packham wrote:
> The last caller to gup_pud_range was removed in commit c2febafc6773
> ("mm: convert generic code to 5-level paging"). Mark it as unused to
> silence a warning from gcc.
>
> Signed-off-by: Chris Packham
> ---
> I saw this warning whe
gup_p4d_range() should call gup_pud_range(), not itself.
Signed-off-by: Kirill A. Shutemov
Reported-by: Chris Packham
Fixes: c2febafc6773 ("mm: convert generic code to 5-level paging")
---
mm/gup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/gup.c b/mm/gup.c
index c74
Hi,
On Sunday 12 March 2017 02:48 PM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Thu, Mar 9, 2017 at 5:26 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Thursday 09 March 2017 05:03 PM, Jaehoon Chung wrote:
>>> Make the "samsung" directory and move the Samsung specific files to
>>> there for
From: Limeng
So far, there is not a sysfs interface for user space code to
check the TPM hardware version(TPM1.x or TPM2). So, add a
file named description in /sys/class/tpm/tpmX/ to show it.
Signed-off-by: Meng Li
---
drivers/char/tpm/tpm-chip.c | 85
On Mon, Mar 13, 2017 at 09:28:34AM +0530, SIMRAN SINGHAL wrote:
> On Mon, Mar 13, 2017 at 12:03 AM, Alison Schofield
> wrote:
> > On Sun, Mar 12, 2017 at 07:02:50PM +0530, simran singhal wrote:
> >> The IIO subsystem is redefining iio_dev->mlock to be used by
> >> the IIO core only for protecting
201 - 300 of 350 matches
Mail list logo
