Fri, May 19, 2017 at 07:17:59PM CEST, xiyou.wangc...@gmail.com wrote:
>On Thu, May 18, 2017 at 7:07 AM, Colin King wrote:
>> diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
>> index 4020b8d932a1..82ebdc3fcb2e 100644
>> --- a/net/sched/cls_api.c
>> +++ b/net/sched/cls_api.c
>> @@ -511,6 +511
XHCI specification 1.1 does not require xHCI 1.0 compliant controllers
to always enable hardware USB2 LPM.
However, the current xHCI driver always enable it by setting HLE=1 when
seeing HLC=1. This makes certain xHCI controllers that have broken USB2
HW LPM fail to work as there is no way to disabl
On Fri 19-05-17 09:46:23, Guenter Roeck wrote:
> Hi,
>
> my qemu tests of next-20170519 show the following results:
> total: 122 pass: 30 fail: 92
>
> I won't bother listing all of the failures; they are available at
> http://kerneltests.org/builders. I bisected one (openrisc, because
> it
> Il giorno 19 mag 2017, alle ore 16:54, Tejun Heo ha scritto:
>
> Hello, Paolo.
>
> On Fri, May 19, 2017 at 10:39:08AM +0200, Paolo Valente wrote:
>> Operations on blkg objects in blk-cgroup are protected with the
>> request_queue lock, which is no more the lock that protects
>> I/O-scheduler
On Fri 19-05-17 17:46:58, John Hubbard wrote:
> On 05/17/2017 01:09 AM, Michal Hocko wrote:
> >From: Michal Hocko
> >
> >While converting drm_[cm]alloc* helpers to kvmalloc* variants Chris
> >Wilson has wondered why we want to try kmalloc before vmalloc fallback
> >even for larger allocations requ
From: Wanlong Gao
Module name has a limited length, but currently the build system
allows the build finishing even if the module name is too long.
CC
/root/kprobe_example/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz.mod.o
/root/kprobe_example/abcdefghijk
rdac_failover_get references struct rdac_controller as
ctlr->ms_sdev->handler_data->ctlr for no apparent reason. Besides being
inefficient this also introduces a null-pointer dereference as
send_mode_select() sets ctlr->ms_sdev to NULL before calling
rdac_failover_get():
[ 18.432550] device-mapp
On Fri, May 19, 2017 at 05:54:37PM +, mario.limoncie...@dell.com wrote:
> >
> > It happens occasionally when you reboot the machine when a device is
> > connected but seems to be dependent on the BIOS version. Since it is the
> > BIOS who is supposed to enumerated these devices, I suspect that
On Fri, 2017-05-19 at 09:36 +, Dashi DS1 Cao wrote:
> It seems there is a race of multiple "fc_starget_delete" of the same
> rport, thus of the same SCSI host. The race leads to the race of
> scsi_remove_target and it cannot be prevented by the code snippet
> alone, even of the most recent
>
On Fri, May 19, 2017 at 12:13:26PM -0500, Christoph Lameter wrote:
> On Fri, 19 May 2017, Marcelo Tosatti wrote:
>
> > Use-case: realtime application on an isolated core which for some reason
> > updates vmstatistics.
>
> Ok that is already only happening every 2 seconds by default and that
> int
On Fri, May 19, 2017 at 02:44:38PM -0700, Julius Werner wrote:
> The recent coreboot memory console update (firmware: google: memconsole:
> Adapt to new coreboot ring buffer format) introduced a small security
> issue in the driver: The new driver implementation parses the memory
> console structur
On Fri, May 19, 2017 at 06:51:44PM +0200, Enric Balletbo i Serra wrote:
> We don't need to bitbang these pins anymore, instead we muxed these
> pins as SPI, after this change, done in commit 6c69f726, we introduced
> the following error:
>
> pinctrl-single 44e10800.pinmux: pin PIN85 already reque
On Fri, May 19, 2017 at 06:51:43PM +0200, Enric Balletbo i Serra wrote:
> The second version of the hardware moved the card detect pin from gpio0_6
> to gpio1_9, as we won't support the first hardware version fix the pinmux
> configuration of this pin.
>
> Fixes: 8584d4fc ("ARM: dts: am335x-sl50:
On Fri, May 19, 2017 at 01:38:11PM +0300, Igor Stoppa wrote:
> Dynamically allocated variables can be made read only,
> after they have been initialized, provided that they reside in memory
> pages devoid of any RW data.
>
> The implementation supplies means to create independent pools of memory,
On (05/19/17 15:02), Petr Mladek wrote:
> > [..]
> >
> > > the problem is that
> > >
> > > `PRINTK_NMI_CONTEXT_MASK || PRINTK_NMI_DEFERRED_CONTEXT_MASK' is 0x01
> >
> > d'oh... forgot to copy-paste this...
>
> Grrr, thanks a lot for chasing this down and I am sorry for the troubles.
no worri
On Fri, May 19 2017, 07:35 PM, mario.limoncie...@dell.com wrote:
> Here's my setup:
> System: I'm using is an XPS 9350 (Has Alpine Ridge). It's got NVM 16.0. BIOS
> 1.4.13 TBT Device: Dell TB16 (which has AR in the cable and in dock - both
> NVM 16.0).
>
Is it BIOS assist or native enumeration?
Commit 5b5e0928f742 ("lib/vsprintf.c: remove %Z support") removed some
usages of format %Z but forgot "%.2Zx". This makes clang 4.0 reports a
-Wformat-extra-args warning because it does not know about %Z.
Replace %Z with %z.
Cc: sta...@vger.kernel.org # v4.11+
Signed-off-by: Nicolas Iooss
---
d
When compiling with -Wsuggest-attribute=format, gcc complains that some
functions in kernel/printk/printk_safe.c transmit their argument to
printf-like functions without having a printf attribute. Silence these
warnings by adding relevant __printf attributes.
Signed-off-by: Nicolas Iooss
---
ker
Hi,
On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > Looks like you running your patched kernel?
> That's right.
>
>
> >>> CONFIG_RMI4_CORE=m
> >>> CONFIG_RMI4_I2C=m
> >>> CONFIG_RMI4_SPI=m
> >>> # CONFIG_RMI4_SMB is not set
> >
> > This is your issue I believe.
>
> Indeed, enabling th
>-Original Message-
>From: Cheng, Collins
>Sent: Saturday, May 20, 2017 12:53 AM
>To: Alexander Duyck; Alex Williamson
>Cc: Bjorn Helgaas; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
>Deucher, Alexander; Zytaruk, Kelly; Yinghai Lu
>Subject: RE: [PATCH] PCI: Make SR-IOV capabl
On Fri, 2017-05-19 at 10:04 +0200, Arnd Bergmann wrote:
> The lpfc_nvmeio_data() tracing helper always takes a format string and
> three additional arguments.
No it doesn't. It takes a format and arguments.
I don't disagree with the patch, just the characterization
of the lpfc_mvmeio_data call i
Hi Kelly,
This issue also happens in "not SR-IOV capable" SBIOS. It seems some "not
SR-IOV capable" SBIOS will directly report error in system BIOS boot stage and
doesn't boot to OS. But other "not SR-IOV capable" SBIOS would not report error
and boot to Linux.
-Collins Cheng
-Original M
On 20/05/17 00:21, Linus Torvalds wrote:
> So I noticed that my diffstat didn't match either the KVM or the Xen pull.
>
> The *reason* seems to be that both Radim and Juergen have enabled the
> "patience" diff, because if I add "--patience" to the diff line, I get
> the same numbers you guys repor
memcg_propagate_slab_attrs() abuses the sysfs attribute file functions to
propagate settings from the root kmem_cache to a newly created
kmem_cache. It does that with:
attr->show(root, buf);
attr->store(new, buf, strlen(bug);
Aside of being a lazy and absurd hackery this is broken becau
Adding __printf attributes helps to detect errors in printf format
strings at build time.
Signed-off-by: Nicolas Iooss
---
drivers/scsi/pcmcia/nsp_cs.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/pcmcia/nsp_cs.c b/drivers/scsi/pcmcia/nsp_cs.c
index 5fb6
nsp32_message() and nsp32_dmessage() use printf format strings in order
to format a message. Adding __printf attributes helps to detect errors
in such format strings at build time, like:
drivers/scsi/nsp32.c:3314:23: error: format '%ld' expects argument
of type 'long int', but argument 6 h
When compiling with -Wsuggest-attribute=format in HOSTCFLAGS, gcc
complains that error_with_pos() may be declared with a printf format
attribute:
scripts/genksyms/genksyms.c:726:3: warning: function might be
possible candidate for ‘gnu_printf’ format attribute
[-Wsuggest-attribute=form
On Sat, 2017-05-20 at 13:16 +0200, Nicolas Iooss wrote:
> nsp32_message() and nsp32_dmessage() use printf format strings in order
> to format a message. Adding __printf attributes helps to detect errors
> in such format strings at build time, like:
>
> drivers/scsi/nsp32.c:3314:23: error: form
Am 20.05.2017 um 01:48 schrieb Lyude:
This is the first part of me going through and cleaning up the IRQ handling
code for radeon, since after taking a look at it the other day while trying to
debug something I realized basically all of the code was copy pasted
everywhere, and quite difficult to
This is v2 post.
This patchset is trying to fix a bug that SGI UV system casually hang
during boot with KASLR enabled. The root cause is that mm KASLR adapts
size of the direct mapping section only based on the system RAM size.
Then later when map SGI UV MMIOH region into the direct mapping during
The SGI BIOS adds UVsystab, and only systems running SGI BIOS
(and now HPE Hawks2) will have UVsystab. And UVsystab is detected in
efi_init() which is at very early stage. So introduce a new helper
function is_early_uv_system() for later usage.
Signed-off-by: Baoquan He
Cc: Thomas Gleixner
Cc: I
On SGI UV system, kernel casually hang with kaslr enabled.
The back trace is:
kernel BUG at arch/x86/mm/init_64.c:311!
invalid opcode: [#1] SMP
[...]
RIP: 0010:__init_extra_mapping+0x188/0x196
[...]
Call Trace:
init_extra_mapping_uc+0x13/0x15
map_high+0x67/0x75
map_mmioh_high_uv3+0x20a/0x
On Mon, May 15, 2017 at 12:51:45PM -0400, Stefan Berger wrote:
> Implement the request_locality function. To set the locality on the
> backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
> a command to the backend to set the locality for the next commands.
>
> To avoid recursing
On Mon, May 15, 2017 at 11:56:51AM -0400, Stefan Berger wrote:
> On 05/15/2017 08:41 AM, Jarkko Sakkinen wrote:
> > On Wed, May 10, 2017 at 07:54:22PM -0400, Stefan Berger wrote:
> > > Implement the request_locality function. To set the locality on the
> > > backend we define vendor-specific TPM 1.
On Mon, May 15, 2017 at 03:18:41PM +0200, Roberto Sassu wrote:
>
>
> On 5/15/2017 12:36 PM, Jarkko Sakkinen wrote:
> > On Fri, May 05, 2017 at 04:21:48PM +0200, Roberto Sassu wrote:
> > > This function allows TPM users to know which algorithms the TPM supports.
> > > It stores the algorithms in a
I'm announcing the release of the 3.18.54 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 274ec43fc6ba..f44ed53ab175 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 53
+SUBLEVEL = 54
EXTRAVERSION =
NAME = Diseased Newt
diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
ind
diff --git a/Makefile b/Makefile
index e6c7990497e7..dc5df61ea4be 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 68
+SUBLEVEL = 69
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/arm/kvm/psci.c b/arch/arm/kvm/psci.c
index a9b3b905e661..443
I'm announcing the release of the 4.4.69 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.9.29 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
--
Note, this is the LAST 4.10.y kernel to be released, it is now
end-of-life. You must move to the 4.11.y kernel series now.
--
I'm announcing the release of the 4.10.17 kernel.
All users of the 4.10 kernel series must upgrade.
The updated 4.10.y git tree can be
diff --git a/Makefile b/Makefile
index 9460a63087b8..c12e501a18b8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 28
+SUBLEVEL = 29
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/arm/kvm/psci.c b/arch/arm/kvm/psci.c
index c2b131527a64..a08d7
diff --git a/Makefile b/Makefile
index e3e60e71fa78..2e8b04bd180e 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 10
-SUBLEVEL = 16
+SUBLEVEL = 17
EXTRAVERSION =
NAME = Fearless Coyote
diff --git a/arch/arm/kvm/psci.c b/arch/arm/kvm/psci.c
index c2b131527a64..a08
I'm announcing the release of the 4.11.2 kernel.
All users of the 4.11 kernel series must upgrade.
The updated 4.11.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.11.y
and can be browsed at the normal kernel.org git web browser:
Signed-off-by: Bram Vlerick
---
drivers/input/mouse/gpio_mouse.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/input/mouse/gpio_mouse.c b/drivers/input/mouse/gpio_mouse.c
index ced07391304b..2fc8ddaf0175 100644
--- a/drivers/input/mouse/gpio_mouse.c
+++ b/dri
Hi Kevin,
Am 18.05.2017 um 00:34 schrieb Kevin Hilman:
> Andreas Färber writes:
>> Am 15.05.2017 um 10:16 schrieb Neil Armstrong:
>>> It's not perfect, but now it's done, live with it, this has already been
>>> discussed.
>>
>> No.
>>
>> Copy&pasting your comment N times does not make it any mor
On Sat, May 20, 2017 at 12:52:03PM +0200, Thomas Gleixner wrote:
> This should be rewritten proper by adding a propagate() callback to those
> slub_attributes which must be propagated and avoid that insane conversion
> to and from ASCII
Exactly..
>, but that's too large for a hot fix.
What made
On Wed, May 17, 2017 at 10:42:35AM +0200, Roberto Sassu wrote:
> On 5/15/2017 3:18 PM, Roberto Sassu wrote:
> >
> >
> > On 5/15/2017 12:36 PM, Jarkko Sakkinen wrote:
> > > On Fri, May 05, 2017 at 04:21:48PM +0200, Roberto Sassu wrote:
> > > > This function allows TPM users to know which algorithm
Hi Bjorn,
Steve found a case where the !CONFIG_PCI_MSI stub for pci_alloc_irq_vectors
did the wrong thing when used with the newly converted xhci driver. While
the PCI code has been wrong since day 1 the fact that a newly converted
drivers triggers it makes it a regression in this cycle.
We need to return an error for any call that asks for MSI / MSI-X
vectors only, so that non-trivial fallback logic can work properly.
Signed-off-by: Christoph Hellwig
Reported-by: Steven Rostedt
Fixes: aff17164 ("PCI: Provide sensible IRQ vector alloc/free routines")
---
include/linux/pci.h | 2
On Mon, May 15, 2017 at 04:22:22PM +0200, Roberto Sassu wrote:
> On 5/15/2017 1:16 PM, Jarkko Sakkinen wrote:
> > On Fri, May 05, 2017 at 04:21:49PM +0200, Roberto Sassu wrote:
> > > tpm_pcr_algorithms() returns to its callers the IDs of the hash algorithms
> > > supported by the TPM. This patch in
Properly mark 4.10 as being EOL on the website.
Signed-off-by: Greg Kroah-Hartman
diff --git a/pelicanconf.py b/pelicanconf.py
index d0ec28210bc9..dbfe46b637bb 100644
--- a/pelicanconf.py
+++ b/pelicanconf.py
@@ -26,7 +26,7 @@ sys.path.append('./')
from plugins import releases
LONGTERM_KERN
This patch series add hardware CRC32 ("Ethernet") calculation support
for STMicroelectronics STM32F429.
Polynomial and key setting are not supported, key is fixed as 0x4C11DB7
and poly is 0x.
Module is tested on STM32F429-disco board with crypto testmgr using
cases within the key 0xFF
This patch adds CRC (CRC32 Crypto) support for STM32F4 series.
As an hardware limitation polynomial and key setting are not supported.
They are fixed as 0x4C11DB7 (poly) and 0x (key).
CRC32C Castagnoli algorithm is not used.
Signed-off-by: Cosar Dindar
---
drivers/crypto/stm32/stm32_crc
Add device tree binding for STM32F4.
Signed-off-by: Cosar Dindar
---
Documentation/devicetree/bindings/crypto/st,stm32-crc.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/crypto/st,stm32-crc.txt
b/Documentation/devicetree/bindings/cr
Enable the CRC32 crypto on stm32429i-eval board.
Signed-off-by: Cosar Dindar
---
arch/arm/boot/dts/stm32429i-eval.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index b633114..360fb19 100644
--- a/arch/arm/
Add CRC32 Crypto support to stm32f429.
Signed-off-by: Cosar Dindar
---
arch/arm/boot/dts/stm32f429.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index b2a2b5c..18343de 100644
--- a/arch/arm/boot/dts/stm32f429.d
Enable the CRC32 crypto on stm32429-disco board.
Signed-off-by: Cosar Dindar
---
arch/arm/boot/dts/stm32f429-disco.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429-disco.dts
b/arch/arm/boot/dts/stm32f429-disco.dts
index 191fa50..ae47cde 100644
--- a/arch/a
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It will fix:
* orion_wdt compile-test dependencies
* sama5d4_wdt: WDDIS handling and a race confition
* pcwd_usb: fix NULL-deref at probe
* cadence_wdt: fix timeout setting
* wdt_pci: fix build e
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-4.12-rc2
for you to fetch changes up to 9434cec
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-4.12-rc2
for you to fetch changes up to b51e0ceed1f93a1eda3
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.12-rc2
for you to fetch changes up to 66ea5974b36
Am 15.05.2017 um 22:24 schrieb Martin Blumenstingl:
> On Mon, May 15, 2017 at 9:10 PM, Andreas Färber wrote:
>> Hi Neil,
>>
>> Am 15.05.2017 um 10:16 schrieb Neil Armstrong:
>>> Hi Andreas,
>>>
>>> On 05/13/2017 04:33 PM, Andreas Färber wrote:
Hello Kevin,
This series fixes several
On 05/20/2017 12:26 AM, Michal Hocko wrote:
On Fri 19-05-17 09:46:23, Guenter Roeck wrote:
Hi,
my qemu tests of next-20170519 show the following results:
total: 122 pass: 30 fail: 92
I won't bother listing all of the failures; they are available at
http://kerneltests.org/builders. I bi
On Sat, 20 May 2017 06:16:45 -0700
Christoph Hellwig wrote:
> On Sat, May 20, 2017 at 12:52:03PM +0200, Thomas Gleixner wrote:
> > This should be rewritten proper by adding a propagate() callback to those
> > slub_attributes which must be propagated and avoid that insane conversion
> > to and fro
Collins,
Okay, good to know.
Is there a common solution that can handle all cases?
Thanks,
Kelly
>-Original Message-
>From: Cheng, Collins
>Sent: Saturday, May 20, 2017 6:38 AM
>To: Zytaruk, Kelly; Alexander Duyck; Alex Williamson
>Cc: Bjorn Helgaas; linux-...@vger.kernel.org; linux-kern
From: Markus Elfring
Date: Sat, 20 May 2017 16:25:04 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Improve a size determination in four functions
Delete error messages for failed memory allocations in five functions
drivers/vho
From: Markus Elfring
Date: Sat, 20 May 2017 13:48:44 +0200
Replace the specification of four data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Sat, 20 May 2017 15:50:30 +0200
Omit seven extra messages for memory allocation failures in these functions.
This issue was detected by using the Coccinelle software.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Hi All,
I'm trying to boot a CHIPPro with the stock 4.12 rc1 kernel. If I make
no modifications to the sun5i-gr8-chip-pro.dtb the kernel boots but
can't find the root partition.
So I added the partitions to the dts file
diff --git a/arch/arm/boot/dts/sun5i-gr8-chip-pro.dts
b/arch/arm/boot/d
Le Sat, 20 May 2017 08:49:04 -0600,
Angus Ainslie a écrit :
> Hi All,
>
> I'm trying to boot a CHIPPro with the stock 4.12 rc1 kernel. If I make
> no modifications to the sun5i-gr8-chip-pro.dtb the kernel boots but
> can't find the root partition.
>
> So I added the partitions to the dts file
Hi Kevin,
Am 17.05.2017 um 23:46 schrieb Kevin Hilman:
> Andreas Färber writes:
>> This series fixes several cosmetic issues, on top of your for-next branch.
>>
>> Patches 3-6 rename a node, the rest should all be non-functional changes.
>>
>> PLEASE STOP merging random new nodes at the bottom of
Use of_device_get_match_data() instead of of_match_device().
It allows us to remove the forward declaration of pcs_of_match.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/pinctrl-single.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-si
On 19/05/17 22:57, Guenter Roeck wrote:
On Fri, May 19, 2017 at 2:28 PM, Matthias Kaehlcke wrote:
This fixes the following warning when building with clang:
drivers/iio/light/isl29018.c:808:36: error: variable
'isl29018_acpi_match' is not needed and will not be emitted
[-Werror,-Wunn
Hi,
ping?
This fixes a regression making the driver effectively useless.
-- Sebastian
On Fri, May 05, 2017 at 11:06:50AM +0200, Sebastian Reichel wrote:
> Since v4.9 i2c-tiny-usb generates the below call trace
> and longer works, since it can't communicate with the
> USB device. The reason is,
On Fri, May 19, 2017 at 10:23:53PM -0700, Andy Lutomirski wrote:
> On Fri, May 19, 2017 at 2:35 PM, Josh Poimboeuf wrote:
> > On Fri, May 19, 2017 at 04:29:13PM -0500, Josh Poimboeuf wrote:
> >> > How are you handling control flow?
> >>
> >> Control flow of what?
> >>
> >> > > Here's the struct in
On Fri, 19 May 2017 20:21:54 -0600
Sam Povilus wrote:
> The number of xilinx ps uart should be set by a kernel parameter instead of
> using a #define. This allows the user to set the number of xilinx ps uart
> using only kconfig and not modifying kernel source.
>
> The ps uart is used in Xilnx Z
On 19/05/17 17:01, Mark Brown wrote:
On Thu, Apr 27, 2017 at 07:01:07AM +0100, Jonathan Cameron wrote:
Somewhat of a pain to basically use a random value as the default going
forward. Presumably this isn't the first ever ACPI table to need to
tell use about a reference voltage...
Mark, seen
Hi,
On Tue, May 16, 2017 at 12:08:32AM +0200, Rasmus Villemoes wrote:
> On Sun, May 14 2017, Guenter Roeck wrote:
>
> > On 05/12/2017 05:05 AM, Sebastian Reichel wrote:
> >> On some systems its desirable to have watchdog reboot the system
> >> when it does not come up fast enough. This adds a ker
Hi Stephen,
On Tue, May 16, 2017 at 07:32:09AM +1000, Stephen Rothwell wrote:
> On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote:
> > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote:
> > > There are also 288 commits in next-20170502 that didn't make it into
> > > v4.12-
On 19/05/17 15:47, Nikita Yushchenko wrote:
With current event-only driver, it is not possible for user space
application to know current senses if they don't change since
application starts.
Address that by adding raw access to channels.
Signed-off-by: Nikita Yushchenko
Ideally I'd like Vlad
On 19/05/17 15:48, Nikita Yushchenko wrote:
Currently, driver generates events for channels if new reading differs
from previous one. This "previous value" is initialized to zero, which
results into event if value is constant-one.
Fix that by initializing "previous value" by reading at event ena
On 19/05/17 15:48, Nikita Yushchenko wrote:
Possible values of sensing_mode are encoded with strings and actual
atrings used are not obvious.
strings
Provide a hint by enabling in_voltage_sensing_mode_available attribute.
Signed-off-by: Nikita Yushchenko
Applied to the togreg branch of iio
On 19/05/17 15:48, Nikita Yushchenko wrote:
Reset GPIO is active low.
Currently driver uses gpiod_set_value(1) to clean reset, which depends
on device tree to contain GPIO_ACTIVE_HIGH - that does not match reality.
This fixes driver to use _raw version of gpiod_set_value() to enforce
active-low
The problem is due to 32-bit integer overflow in:
ADAPT_SCALE_BASE and adapt
In dcache_init_early() that is causing the problem. It was not enabled
before 'mm: drop HASH_ADAPT' but is enabled now, and it should follow
right after: "PID hash table entries: 1024 (order: 0, 4096 bytes)"
main()
On Fri, May 19, 2017 at 10:03:59AM +0300, Konstantin Khlebnikov wrote:
> This allows to get rid of unneeded invocations.
>
> Function debug_lockdep_rcu_enabled() becomes really hot if several
> debug options are enabled together with CONFIG_PROVE_RCU.
>
> Hottest path ends with:
> debug_lockdep
Depend on the architecture the device actuall is in, also add
dep on the compile test to ensure continued coverage.
Signed-off-by: Peter Robinson
---
drivers/extcon/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/extcon/Kconfig b/drivers/extcon/Kconfig
index 32f2dc8e4702..6d5
Non-UTF-8 characters are a problem for some terminals and also
make greping harder than necessary - this only switches the
copyright sign to the common (C).
Reported-by: Markus Kreidl
Signed-off-by: Nicholas Mc Guire
---
Found by checkpatch --strict:
CHECK: Invalid UTF-8, patch and commit messa
On Fri, May 19, 2017 at 5:46 AM, Christoph Hellwig wrote:
>
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 33c2b0b77429..5a7fd3b6a7b9 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -1342,7 +1342,7 @@ pci_alloc_irq_vectors_affinity(struct pci_dev *dev,
> unsi
Fix checkpatch issue by adding spaces around the '%' operator
Signed-off-by: Marko Stankovic
---
drivers/staging/vt6655/card.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vt6655/card.c b/drivers/staging/vt6655/card.c
index 5463cf869d1b..f5db2b3d9045 100644
On Sat, May 20, 2017 at 09:49:56AM -0700, Linus Torvalds wrote:
> Side note: why is it doing that " > 1" check, when any value _other_
> than 1 is wrong?
It's the same effect, so either one is fine with me.
> Also, to match the non-MSI implementation, wouldn't it be nicer to
> just write it that
We need to return an error for any call that asks for MSI / MSI-X
vectors only, so that non-trivial fallback logic can work properly.
Also valid dev->irq and use the "correct" errno value based on feedback
from Linus.
Signed-off-by: Christoph Hellwig
Reported-by: Steven Rostedt
Fixes: aff17164
The combo of list_empty() and list_first_entry() can be replaced with
list_first_entry_or_null().
Signed-off-by: Masahiro Yamada
---
drivers/usb/mtu3/mtu3.h | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3.h b/drivers/usb/mtu3/mtu3.h
index aa6fd6
Allow hash tables to scale with memory but at slower pace, when HASH_ADAPT
is provided every time memory quadruples the sizes of hash tables will only
double instead of quadrupling as well. This algorithm starts working only
when memory size reaches a certain point, currently set to 64G.
This is e
Changes from v3 - v4:
- Fixed an issue with 32-bit overflow (adapt is ull now instead ul)
- Added changes suggested by Michal Hocko: use high_limit instead of
a new flag to determine that we should use this new scaling.
Pavel Tatashin (1):
mm: Adaptive hash table scaling
mm/page_alloc.c | 19
On Tue, May 16, 2017 at 10:06 PM, Krzysztof Kozlowski wrote:
> Exynos pinctrl drivers contain pretty big per-SoC data structures. The
> pinctrl-exynos object file contained code and data for both ARMv7 and
> ARMv8 SoCs thus it grew big. There will not be a shared image between
> ARMv7 and ARMv8
On Sat, May 20, 2017 at 07:12:13PM +0200, Linus Walleij wrote:
> On Tue, May 16, 2017 at 10:06 PM, Krzysztof Kozlowski wrote:
>
> > Exynos pinctrl drivers contain pretty big per-SoC data structures. The
> > pinctrl-exynos object file contained code and data for both ARMv7 and
> > ARMv8 SoCs thus
On Sat, May 20, 2017 at 11:20:34AM -0500, Josh Poimboeuf wrote:
>But then, if we're going that far, why not just have objtool reformat
>the data into something much simpler? It already has the knowledge
>to do so. Then we don't have to jump through all those hoops to
>justify jump
Hi Philippe,
2017-05-19 21:17 GMT+09:00 Philippe CORNU :
>
>
> On 05/19/2017 09:49 AM, Julia Lawall wrote:
>> On line 466, the preceeding comment suggests that the second constant
>> should start with VS rather than HS again.
>>
>> julia
>>
>> -- Forwarded message --
>> Date: Fri,
On Sat, May 20, 2017 at 11:59:50AM +0200, Benjamin Tissoires wrote:
> Hi,
>
> On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > > Looks like you running your patched kernel?
> > That's right.
> >
> >
> > >>> CONFIG_RMI4_CORE=m
> > >>> CONFIG_RMI4_I2C=m
> > >>> CONFIG_RMI4_SPI=m
> > >>> #
1 - 100 of 200 matches
Mail list logo
