Re: [PATCH v3 0/4] sparc64: Jump to boot prom from console on panic

On 2/1/2017 1:50 PM, David Miller wrote: From: Vijay Kumar Date: Wed, 1 Feb 2017 11:34:36 -0800 Currently Stop-A (L1A) does not make the kernel switch to OBP on panic. This is intentional, the kernel prints a message telling the user to press break (L1-A) if they

Re: [PATCH v3 0/4] sparc64: Jump to boot prom from console on panic

On 2/1/2017 1:50 PM, David Miller wrote: From: Vijay Kumar Date: Wed, 1 Feb 2017 11:34:36 -0800 Currently Stop-A (L1A) does not make the kernel switch to OBP on panic. This is intentional, the kernel prints a message telling the user to press break (L1-A) if they want to drop out of the

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 12:51 -0800, Cong Wang wrote: > On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: > > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: > > > >> > >> The context is process context (TX path before hitting qdisc), and > >> BH is not disabled, so

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 12:51 -0800, Cong Wang wrote: > On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: > > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: > > > >> > >> The context is process context (TX path before hitting qdisc), and > >> BH is not disabled, so in_interrupt() doesn't

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

> What a poorly chosen name though... in Ethernet world, port mirroring > means the ability to capture traffic from a vector of ports and copying > it verbatim (or sampled) towards a capture port, aka the mirror port... Ack. We should avoid "port mirroring" in what ever patch we decide upon.

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

> What a poorly chosen name though... in Ethernet world, port mirroring > means the ability to capture traffic from a vector of ports and copying > it verbatim (or sampled) towards a capture port, aka the mirror port... Ack. We should avoid "port mirroring" in what ever patch we decide upon.

[PATCH v2 1/3] locking/spinlock_debug: Reduce lockup suspected message clutter

When the debug spinlock code detects a lockup, it will print out an error messages as well as the backtraces of all the CPUs. However, if more than one CPUs are waiting on that lock, multiple lockup messages will be printed leading to garbled output. To reduce clutter in the console log, now only

[PATCH v2 1/3] locking/spinlock_debug: Reduce lockup suspected message clutter

When the debug spinlock code detects a lockup, it will print out an error messages as well as the backtraces of all the CPUs. However, if more than one CPUs are waiting on that lock, multiple lockup messages will be printed leading to garbled output. To reduce clutter in the console log, now only

Re: [PATCH v9 6/8] drivers:input:ads7846(+tsc2046): fix spi module table

Hello Nikolaus, On 02/01/2017 05:20 PM, H. Nikolaus Schaller wrote: > Hi Dmitry, Javier, > >> Am 29.01.2017 um 19:25 schrieb H. Nikolaus Schaller : >> >> Hi Dmitry, >> >>> Am 29.01.2017 um 19:01 schrieb Dmitry Torokhov : >>> >>> On Sun, Jan 29, 2017

Re: [PATCH v9 6/8] drivers:input:ads7846(+tsc2046): fix spi module table

Hello Nikolaus, On 02/01/2017 05:20 PM, H. Nikolaus Schaller wrote: > Hi Dmitry, Javier, > >> Am 29.01.2017 um 19:25 schrieb H. Nikolaus Schaller : >> >> Hi Dmitry, >> >>> Am 29.01.2017 um 19:01 schrieb Dmitry Torokhov : >>> >>> On Sun, Jan 29, 2017 at 09:39:39AM +0100, H. Nikolaus Schaller

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

> We would need a tri-state device tree properly: > > 1. Not defined - do nothing > 2. Defined as 0 -> explicitly disable port mirroring > 3. Defined as 1 -> explicitly enable port mirriring > > The "net-phy-lane-swap" only fulfills points 1 and 3 above. > > In my use case I do need point 2.

[PATCH v2 0/3] locking/spinlock_debug: Change it to a mostly fair lock

v1->v2: - Pack lockup and break_lock into a single 4-byte slot so as not to in increase spinlock size when GENERIC_LOCKBREAK is on. Hopefully that will be enough to fix a frame size too large warning in 0-day build. - Add a new patch to disable GENERIC_LOCKBREAK when

[PATCH v2 0/3] locking/spinlock_debug: Change it to a mostly fair lock

v1->v2: - Pack lockup and break_lock into a single 4-byte slot so as not to in increase spinlock size when GENERIC_LOCKBREAK is on. Hopefully that will be enough to fix a frame size too large warning in 0-day build. - Add a new patch to disable GENERIC_LOCKBREAK when

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

> We would need a tri-state device tree properly: > > 1. Not defined - do nothing > 2. Defined as 0 -> explicitly disable port mirroring > 3. Defined as 1 -> explicitly enable port mirriring > > The "net-phy-lane-swap" only fulfills points 1 and 3 above. > > In my use case I do need point 2.

[PATCH v2 2/3] locking/spinlock_debug: Reduce lock cacheline contention

The debug spinlock code is a basic TATAS unfair lock irrespective of what the underlying architecture specific spinlock implementation is. As a result, it is sometimes possible to trigger a false positive "lockup suspected" warning with all the cpu backtraces. This patch re-implements the debug

[PATCH v2 2/3] locking/spinlock_debug: Reduce lock cacheline contention

The debug spinlock code is a basic TATAS unfair lock irrespective of what the underlying architecture specific spinlock implementation is. As a result, it is sometimes possible to trigger a false positive "lockup suspected" warning with all the cpu backtraces. This patch re-implements the debug

[PATCH v2 3/3] locking/spinlock: Disable GENERIC_LOCKBREAK when DEBUG_LOCK_ALLOC is on

The break_lock variable defined when GENERIC_LOCKBREAK is on is used only in kernel/locking/spinlock.c when defined(CONFIG_GENERIC_LOCKBREAK) && !defined(CONFIG_DEBUG_LOCK_ALLOC). As a result, there is no point in enabling GENERIC_LOCKBREAK to define one more variable in the spinlock structure

[PATCH v2 3/3] locking/spinlock: Disable GENERIC_LOCKBREAK when DEBUG_LOCK_ALLOC is on

The break_lock variable defined when GENERIC_LOCKBREAK is on is used only in kernel/locking/spinlock.c when defined(CONFIG_GENERIC_LOCKBREAK) && !defined(CONFIG_DEBUG_LOCK_ALLOC). As a result, there is no point in enabling GENERIC_LOCKBREAK to define one more variable in the spinlock structure

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

On 02/01/2017 01:05 PM, Lukasz Majewski wrote: > Dear All, > > Thanks for prompt reply. > >> On 02/01/2017 09:16 AM, Andrew Lunn wrote: >>> On Wed, Feb 01, 2017 at 03:43:35PM +0100, Lukasz Majewski wrote: This patch adds support for enabling or disabling the port mirroring feature of

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

On 02/01/2017 01:05 PM, Lukasz Majewski wrote: > Dear All, > > Thanks for prompt reply. > >> On 02/01/2017 09:16 AM, Andrew Lunn wrote: >>> On Wed, Feb 01, 2017 at 03:43:35PM +0100, Lukasz Majewski wrote: This patch adds support for enabling or disabling the port mirroring feature of

Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness

On 1 February 2017 at 20:34, Joe Perches wrote: > On Wed, 2017-02-01 at 19:53 +, Ard Biesheuvel wrote: >> On 1 February 2017 at 19:49, Joe Perches wrote: > [] >> > Or maybe add a BUILD_BUG_ON something like: >> > >> > #define order_base_2(n)

Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness

On 1 February 2017 at 20:34, Joe Perches wrote: > On Wed, 2017-02-01 at 19:53 +, Ard Biesheuvel wrote: >> On 1 February 2017 at 19:49, Joe Perches wrote: > [] >> > Or maybe add a BUILD_BUG_ON something like: >> > >> > #define order_base_2(n) \

Re: [PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

On 2/1/2017 10:45 AM, Ard Biesheuvel wrote: Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), after which unaligned accesses to RAM are no longer supported. Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the kernel") fixed an issue in the memory map

Re: [PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

On 2/1/2017 10:45 AM, Ard Biesheuvel wrote: Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), after which unaligned accesses to RAM are no longer supported. Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the kernel") fixed an issue in the memory map

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

Dear All, Thanks for prompt reply. > On 02/01/2017 09:16 AM, Andrew Lunn wrote: > > On Wed, Feb 01, 2017 at 03:43:35PM +0100, Lukasz Majewski wrote: > >> This patch adds support for enabling or disabling the port > >> mirroring feature of the DP83867 TI's PHY device. > >> > >> One use case is

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

Dear All, Thanks for prompt reply. > On 02/01/2017 09:16 AM, Andrew Lunn wrote: > > On Wed, Feb 01, 2017 at 03:43:35PM +0100, Lukasz Majewski wrote: > >> This patch adds support for enabling or disabling the port > >> mirroring feature of the DP83867 TI's PHY device. > >> > >> One use case is

Re: [PATCH] initity: try to improve __nocapture annotations

On Wed, Feb 1, 2017 at 5:11 PM, Arnd Bergmann wrote: > There are some additional declarations that got missed in the original patch, > and some annotated functions that use the pointer is a correct but nonobvious > way: > > mm/kasan/kasan.c: In function 'memmove': >

Re: [PATCH] initity: try to improve __nocapture annotations

On Wed, Feb 1, 2017 at 5:11 PM, Arnd Bergmann wrote: > There are some additional declarations that got missed in the original patch, > and some annotated functions that use the pointer is a correct but nonobvious > way: > > mm/kasan/kasan.c: In function 'memmove': > mm/kasan/kasan.c:346:7: error:

Re: [PATCH] stmmac: Discard masked flags in interrupt status register

From: Alexey Brodkin Date: Wed, 1 Feb 2017 20:22:22 + > May we have that one back-ported to stable branches starting from 4.8.x? > > That issue started to appear due to a change from pr_debug() to pr_info() in > commit > 70523e639bf8 ("drivers: net: stmmac:

Re: [PATCH] stmmac: Discard masked flags in interrupt status register

From: Alexey Brodkin Date: Wed, 1 Feb 2017 20:22:22 + > May we have that one back-ported to stable branches starting from 4.8.x? > > That issue started to appear due to a change from pr_debug() to pr_info() in > commit > 70523e639bf8 ("drivers: net: stmmac: reworking the PCS code.").

Re: [PATCH v4 00/15] livepatch: hybrid consistency model

On Wed, 1 Feb 2017, Josh Poimboeuf wrote: > If there are no more comments, it would be great to get these patches in > for the 4.11 merge window. Any objections to that? That'd mean that the exposure in -next would be really short, which I'd like to avoid. I'd love to tentatively target 4.12

Re: [PATCH v4 00/15] livepatch: hybrid consistency model

On Wed, 1 Feb 2017, Josh Poimboeuf wrote: > If there are no more comments, it would be great to get these patches in > for the 4.11 merge window. Any objections to that? That'd mean that the exposure in -next would be really short, which I'd like to avoid. I'd love to tentatively target 4.12

[PATCH] Staging: ks7010: Fix tabs in ks_hostif.h.

Convert spaces to tabs in ks_hostif.h, according to the checkpatch.pl script. Signed-off-by: Logan Gorence --- drivers/staging/ks7010/ks_hostif.h | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git

[PATCH] Staging: ks7010: Fix tabs in ks_hostif.h.

Convert spaces to tabs in ks_hostif.h, according to the checkpatch.pl script. Signed-off-by: Logan Gorence --- drivers/staging/ks7010/ks_hostif.h | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/drivers/staging/ks7010/ks_hostif.h

Re: [PATCH v2 0/4] Use build registers for getting numbers of interrupts

On 01/31/2017 03:45 AM, Yuriy Kolerov wrote: > A summary: > > * Use build registers for getting numbers of interrupts both for > core interrupt controller and for IDU interrupt controller. > * Set a default priority for all core interrupt to prevent > unexpected switching of banks of

Re: [PATCH v2 0/4] Use build registers for getting numbers of interrupts

On 01/31/2017 03:45 AM, Yuriy Kolerov wrote: > A summary: > > * Use build registers for getting numbers of interrupts both for > core interrupt controller and for IDU interrupt controller. > * Set a default priority for all core interrupt to prevent > unexpected switching of banks of

RE: Dell XPS13: MCE (Hardware Error) reported

Hi Paul, > Mario, there are at least two more firmware bugs [4][5][6]. Having fast > suspend and resume says something about the quality of a device. If the Dell > XPS13 9360 is supposed to compete with Apple devices, and Google > Chromebooks, then this should be improved in my opinion. Do you

RE: Dell XPS13: MCE (Hardware Error) reported

Hi Paul, > Mario, there are at least two more firmware bugs [4][5][6]. Having fast > suspend and resume says something about the quality of a device. If the Dell > XPS13 9360 is supposed to compete with Apple devices, and Google > Chromebooks, then this should be improved in my opinion. Do you

Re: [PATCH v4 00/15] livepatch: hybrid consistency model

On Wed, 1 Feb 2017, Josh Poimboeuf wrote: > On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote: > > Here's v4, based on linux-next/master. Mostly minor changes this time, > > primarily due to Petr's v3 comments. > > So far, the only review comments have been related to the first

Re: [PATCH v4 00/15] livepatch: hybrid consistency model

On Wed, 1 Feb 2017, Josh Poimboeuf wrote: > On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote: > > Here's v4, based on linux-next/master. Mostly minor changes this time, > > primarily due to Petr's v3 comments. > > So far, the only review comments have been related to the first

Re: net: suspicious RCU usage in nf_hook

On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: > >> >> The context is process context (TX path before hitting qdisc), and >> BH is not disabled, so in_interrupt() doesn't catch it. Hmm, this >> makes me thinking

Re: net: suspicious RCU usage in nf_hook

On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: > >> >> The context is process context (TX path before hitting qdisc), and >> BH is not disabled, so in_interrupt() doesn't catch it. Hmm, this >> makes me thinking maybe we really need to

[PATCH] [linux-next] arm64: defconfig: resynchronize the defconfig

Defconfig files become unsynchronized over time as Kconfig entries are added, removed, or changed. Making specific changes to the defconfig becomes difficult as unrelated differences can interfere. This problem is easily remedied: make defconfig make savedefconfig cp

[PATCH] [linux-next] arm64: defconfig: resynchronize the defconfig

Defconfig files become unsynchronized over time as Kconfig entries are added, removed, or changed. Making specific changes to the defconfig becomes difficult as unrelated differences can interfere. This problem is easily remedied: make defconfig make savedefconfig cp

[PATCH v2 1/2] iio: pressure: mpl3115: do not rely on structure field ordering

Fixes a regression triggered by a change in the layout of struct iio_chan_spec, but the real bug is in the driver which assumed a specific structure layout in the first place. Hint: the two bits were not OR:ed together as implied by the indentation prior to this patch, there was a comma between

[PATCH v2 2/2] iio: pressure: mpl115: do not rely on structure field ordering

Fixes a regression triggered by a change in the layout of struct iio_chan_spec, but the real bug is in the driver which assumed a specific structure layout in the first place. Hint: the three bits were not OR:ed together as implied by the indentation prior to this patch, there was a comma between

[PATCH v2 0/2] iio: pressure: do not rely on structure field ordering

Hi! v1 -> v2 changes: - improved commit messages - added tested-by tag These two patches are needed to fix some fallout from adding the available attribute. Jonathan, it was a bitch to rebase with that line starting with a #. Please make sure that it stays where it should be in case you decide

[PATCH v2 1/2] iio: pressure: mpl3115: do not rely on structure field ordering

Fixes a regression triggered by a change in the layout of struct iio_chan_spec, but the real bug is in the driver which assumed a specific structure layout in the first place. Hint: the two bits were not OR:ed together as implied by the indentation prior to this patch, there was a comma between

[PATCH v2 2/2] iio: pressure: mpl115: do not rely on structure field ordering

Fixes a regression triggered by a change in the layout of struct iio_chan_spec, but the real bug is in the driver which assumed a specific structure layout in the first place. Hint: the three bits were not OR:ed together as implied by the indentation prior to this patch, there was a comma between

[PATCH v2 0/2] iio: pressure: do not rely on structure field ordering

Hi! v1 -> v2 changes: - improved commit messages - added tested-by tag These two patches are needed to fix some fallout from adding the available attribute. Jonathan, it was a bitch to rebase with that line starting with a #. Please make sure that it stays where it should be in case you decide

[PATCH] ubifs: fix data node size for truncating uncompressed nodes

From: David Oberhollenzer Currently, the function truncate_data_node only updates the destination data node size if compression is used. For uncompressed nodes, the old length is incorrectly retained. This patch makes sure that the length is correctly set when

[PATCH] ubifs: fix data node size for truncating uncompressed nodes

From: David Oberhollenzer Currently, the function truncate_data_node only updates the destination data node size if compression is used. For uncompressed nodes, the old length is incorrectly retained. This patch makes sure that the length is correctly set when compression is disabled.

[PATCH] gpio: Add GPIO support for the ACCES PCI-IDIO-16

The ACCES PCI-IDIO-16 device provides 32 lines of digital I/O (16 lines of optically-isolated digital inputs for AC and DC control signals, and 16 lines of solid state switch digital outputs). An interrupt is generated when any of the inputs change state (low to high or high to low). Input filter

[PATCH] gpio: Add GPIO support for the ACCES PCI-IDIO-16

The ACCES PCI-IDIO-16 device provides 32 lines of digital I/O (16 lines of optically-isolated digital inputs for AC and DC control signals, and 16 lines of solid state switch digital outputs). An interrupt is generated when any of the inputs change state (low to high or high to low). Input filter

Re: [PATCH v2] scsi, block: fix duplicate bdi name registration crashes

On Wed, 2017-02-01 at 11:32 -0800, Dan Williams wrote: > diff --git a/include/linux/genhd.h b/include/linux/genhd.h > index 76f39754e7b0..27e7e12c0c2d 100644 > --- a/include/linux/genhd.h > +++ b/include/linux/genhd.h > @@ -167,6 +167,22 @@ struct blk_integrity { > }; > > #endif /*

Re: [PATCH v2] scsi, block: fix duplicate bdi name registration crashes

On Wed, 2017-02-01 at 11:32 -0800, Dan Williams wrote: > diff --git a/include/linux/genhd.h b/include/linux/genhd.h > index 76f39754e7b0..27e7e12c0c2d 100644 > --- a/include/linux/genhd.h > +++ b/include/linux/genhd.h > @@ -167,6 +167,22 @@ struct blk_integrity { > }; > > #endif /*

Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness

On Wed, 2017-02-01 at 19:53 +, Ard Biesheuvel wrote: > On 1 February 2017 at 19:49, Joe Perches wrote: [] > > Or maybe add a BUILD_BUG_ON something like: > > > > #define order_base_2(n) \ > > ({

Re: [PATCH] fscrypt: properly declare on-stack completion

Am 01.02.2017 um 21:32 schrieb Richard Weinberger: > When a completion is declared on-stack we have to use > COMPLETION_INITIALIZER_ONSTACK(). > > Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs > tree to fs/crypto") > Signed-off-by: Richard Weinberger > >

Re: [PATCH] fscrypt: properly declare on-stack completion

Am 01.02.2017 um 21:32 schrieb Richard Weinberger: > When a completion is declared on-stack we have to use > COMPLETION_INITIALIZER_ONSTACK(). > > Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs > tree to fs/crypto") > Signed-off-by: Richard Weinberger > > --- >

Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness

On Wed, 2017-02-01 at 19:53 +, Ard Biesheuvel wrote: > On 1 February 2017 at 19:49, Joe Perches wrote: [] > > Or maybe add a BUILD_BUG_ON something like: > > > > #define order_base_2(n) \ > > ({

[PATCH] fscrypt: properly declare on-stack completion

When a completion is declared on-stack we have to use COMPLETION_INITIALIZER_ONSTACK(). Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs tree to fs/crypto") Signed-off-by: Richard Weinberger --- fs/crypto/fscrypt_private.h | 2 +- 1 file changed, 1

[PATCH] fscrypt: properly declare on-stack completion

When a completion is declared on-stack we have to use COMPLETION_INITIALIZER_ONSTACK(). Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs tree to fs/crypto") Signed-off-by: Richard Weinberger --- fs/crypto/fscrypt_private.h | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH v4 2nd 2/4] pstore: support multiple pmsg instances

On Mon, Jan 30, 2017 at 5:58 PM, Nobuhiro Iwamatsu wrote: > From: Hiraku Toyooka > > This enables pmsg to deal with multiple instances. One possible > use is content priority control on limited persistent store space. By > using

Re: [PATCH v4 2nd 2/4] pstore: support multiple pmsg instances

On Mon, Jan 30, 2017 at 5:58 PM, Nobuhiro Iwamatsu wrote: > From: Hiraku Toyooka > > This enables pmsg to deal with multiple instances. One possible > use is content priority control on limited persistent store space. By > using different buffers, we can prevent important messages from being >

Re: [PATCH v2] scsi, block: fix duplicate bdi name registration crashes

On Wed, Feb 01, 2017 at 11:32:12AM -0800, Dan Williams wrote: > Warnings of the following form occur because scsi reuses a devt number > while the block layer still has it referenced as the name of the bdi > [1]: > > WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 > sysfs:

Re: [PATCH v2] scsi, block: fix duplicate bdi name registration crashes

On Wed, Feb 01, 2017 at 11:32:12AM -0800, Dan Williams wrote: > Warnings of the following form occur because scsi reuses a devt number > while the block layer still has it referenced as the name of the bdi > [1]: > > WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 > sysfs:

[PATCH] add Hama Hybrid DVB-T Stick support

Adding Hama Hybrid DVB-T Stick support. Technically it's the same device what Terratec Cinergy HT USB XE is. Signed-off-by: Piotr Oleszczyk diff --git a/drivers/media/dvb-core/dvb-usb-ids.h b/drivers/media/dvb-core/dvb-usb-ids.h index 779f422..c90c344 100644 ---

[PATCH] add Hama Hybrid DVB-T Stick support

Adding Hama Hybrid DVB-T Stick support. Technically it's the same device what Terratec Cinergy HT USB XE is. Signed-off-by: Piotr Oleszczyk diff --git a/drivers/media/dvb-core/dvb-usb-ids.h b/drivers/media/dvb-core/dvb-usb-ids.h index 779f422..c90c344 100644 ---

Re: [PATCH v9 6/8] drivers:input:ads7846(+tsc2046): fix spi module table

Hi Dmitry, Javier, > Am 29.01.2017 um 19:25 schrieb H. Nikolaus Schaller : > > Hi Dmitry, > >> Am 29.01.2017 um 19:01 schrieb Dmitry Torokhov : >> >> On Sun, Jan 29, 2017 at 09:39:39AM +0100, H. Nikolaus Schaller wrote: >>> Hi Dmitry, >>> Am

Re: [PATCH v9 6/8] drivers:input:ads7846(+tsc2046): fix spi module table

Hi Dmitry, Javier, > Am 29.01.2017 um 19:25 schrieb H. Nikolaus Schaller : > > Hi Dmitry, > >> Am 29.01.2017 um 19:01 schrieb Dmitry Torokhov : >> >> On Sun, Jan 29, 2017 at 09:39:39AM +0100, H. Nikolaus Schaller wrote: >>> Hi Dmitry, >>> Am 28.01.2017 um 20:35 schrieb Dmitry Torokhov :

RE: [PATCH] stmmac: Discard masked flags in interrupt status register

Hi David, all, > -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Monday, January 30, 2017 2:16 AM > To: alexey.brod...@synopsys.com > Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org; > peppe.cavall...@st.com; fabrice.gasn...@st.com;

RE: [PATCH] stmmac: Discard masked flags in interrupt status register

Hi David, all, > -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Monday, January 30, 2017 2:16 AM > To: alexey.brod...@synopsys.com > Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org; > peppe.cavall...@st.com; fabrice.gasn...@st.com;

Re: [PATCH v6 1/5] lib: Update LZ4 compressor module

On Tue, Jan 31, 2017 at 03:27:44PM -0700, Jonathan Corbet wrote: > On Fri, 27 Jan 2017 23:02:00 +0100 > Sven Schmidt <4ssch...@informatik.uni-hamburg.de> wrote: > > I have one quick question... > > > /* > > + * LZ4_compress_default() > > + * Compresses 'sourceSize' bytes from buffer 'source' >

Re: [PATCH v6 1/5] lib: Update LZ4 compressor module

On Tue, Jan 31, 2017 at 03:27:44PM -0700, Jonathan Corbet wrote: > On Fri, 27 Jan 2017 23:02:00 +0100 > Sven Schmidt <4ssch...@informatik.uni-hamburg.de> wrote: > > I have one quick question... > > > /* > > + * LZ4_compress_default() > > + * Compresses 'sourceSize' bytes from buffer 'source' >

Re: [PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

* Ard Biesheuvel wrote: > On 1 February 2017 at 19:03, Ingo Molnar wrote: > > > > * Ard Biesheuvel wrote: > > > >> Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), > >> after which unaligned

Re: [PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

* Ard Biesheuvel wrote: > On 1 February 2017 at 19:03, Ingo Molnar wrote: > > > > * Ard Biesheuvel wrote: > > > >> Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), > >> after which unaligned accesses to RAM are no longer supported. > >> > >> Commit abfb7b686a3e

irq_work_run called from armv8pmu_handle_irq

Hi All, we would like to understand why irq_work_run() is getting called from armv8pmu_handle_irq() irq handler for arm SoC. Is this irq_work frame work designed to run works from ARMPMU irq handlers? If there are no of drivers using the IRQ WORK frame work, we may see that ARMPMU irq

irq_work_run called from armv8pmu_handle_irq

Hi All, we would like to understand why irq_work_run() is getting called from armv8pmu_handle_irq() irq handler for arm SoC. Is this irq_work frame work designed to run works from ARMPMU irq handlers? If there are no of drivers using the IRQ WORK frame work, we may see that ARMPMU irq

Re: [PATCH] Documentation/sphinx: make targets independent of Sphinx work for HAVE_SPHINX=0

On Mon, 30 Jan 2017 18:58:15 +0200 Jani Nikula wrote: > Make targets that don't depend on Sphinx work without warnings about > missing Sphinx. 'make cleandocs' will work without Sphinx just fine, and > the targets that are no-ops for Sphinx should just be skipped. Move

Re: [PATCH] Documentation/sphinx: make targets independent of Sphinx work for HAVE_SPHINX=0

On Mon, 30 Jan 2017 18:58:15 +0200 Jani Nikula wrote: > Make targets that don't depend on Sphinx work without warnings about > missing Sphinx. 'make cleandocs' will work without Sphinx just fine, and > the targets that are no-ops for Sphinx should just be skipped. Move them > outside of the

Re: [PATCH 0/3] cifs: Better dependencies

Merged into cifs-2.6.git for-next Thanks - this is helpful On Wed, Jan 25, 2017 at 1:26 PM, Pavel Shilovsky wrote: > 2017-01-25 7:06 GMT-08:00 Jean Delvare : >> Hi all, >> >> This is my attempt to fix and improve the dependencies of cifs. >> >> [PATCH

Re: [PATCH 0/3] cifs: Better dependencies

Merged into cifs-2.6.git for-next Thanks - this is helpful On Wed, Jan 25, 2017 at 1:26 PM, Pavel Shilovsky wrote: > 2017-01-25 7:06 GMT-08:00 Jean Delvare : >> Hi all, >> >> This is my attempt to fix and improve the dependencies of cifs. >> >> [PATCH 1/3] cifs: Simplify SMB2 and SMB311

Re: [PATCH v2 0/4] Style fixes: open code obfuscating macros

On Thu, Jan 26, 2017 at 3:00 PM, Logan Gunthorpe wrote: > Hi, > > It's been a couple weeks... Any thoughts on this? My apologies for not responding sooner. A large rework of the core NTB code was done prior to your patches (for IDT NTB support). Unfortunately, after those

Re: [PATCH v2 0/4] Style fixes: open code obfuscating macros

On Thu, Jan 26, 2017 at 3:00 PM, Logan Gunthorpe wrote: > Hi, > > It's been a couple weeks... Any thoughts on this? My apologies for not responding sooner. A large rework of the core NTB code was done prior to your patches (for IDT NTB support). Unfortunately, after those changes this series

RE: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

> I was asking for requirements, not a design proposal. In order to make a > design you need a requirements specification. Here's what I came up with ... not a fully baked list, but should allow for some useful discussion on whether any of these are not really needed, or if there is a glaring

RE: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

> I was asking for requirements, not a design proposal. In order to make a > design you need a requirements specification. Here's what I came up with ... not a fully baked list, but should allow for some useful discussion on whether any of these are not really needed, or if there is a glaring

[PATCH 2/2] [media] exynos-gsc: Add support for NV{16,21,61}M pixel formats

From: Thibault Saunier Those are useful formats that should be handled. Signed-off-by: Thibault Saunier Signed-off-by: Javier Martinez Canillas --- drivers/media/platform/exynos-gsc/gsc-core.c | 27

[PATCH 2/2] [media] exynos-gsc: Add support for NV{16,21,61}M pixel formats

From: Thibault Saunier Those are useful formats that should be handled. Signed-off-by: Thibault Saunier Signed-off-by: Javier Martinez Canillas --- drivers/media/platform/exynos-gsc/gsc-core.c | 27 +++ 1 file changed, 27 insertions(+) diff --git

[PATCH 1/2] [media] exynos-gsc: Do not swap cb/cr for semi planar formats

From: Thibault Saunier In the case of semi planar formats cb and cr are in the same plane in memory, meaning that will be set to 'cb' whatever the format is, and whatever the (packed) order of those components are. Suggested-by: Nicolas Dufresne

[PATCH 1/2] [media] exynos-gsc: Do not swap cb/cr for semi planar formats

From: Thibault Saunier In the case of semi planar formats cb and cr are in the same plane in memory, meaning that will be set to 'cb' whatever the format is, and whatever the (packed) order of those components are. Suggested-by: Nicolas Dufresne Signed-off-by: Thibault Saunier Signed-off-by:

[PATCH 0/2] [media] exynos-gsc: Fix support for NV21 and NV61 formats

Hello, Commit 652bb68018a5 ("[media] exynos-gsc: do proper bytesperline and sizeimage calculation") fixed corrupted frames for most exynos-gsc formats, but even after that patch two issues were still remaining: 1) Frames were still not correct for NV21 and NV61 formats. 2) Y42B format didn't

[PATCH 0/2] [media] exynos-gsc: Fix support for NV21 and NV61 formats

Hello, Commit 652bb68018a5 ("[media] exynos-gsc: do proper bytesperline and sizeimage calculation") fixed corrupted frames for most exynos-gsc formats, but even after that patch two issues were still remaining: 1) Frames were still not correct for NV21 and NV61 formats. 2) Y42B format didn't

Re: [PATCH v2] HID: Add quirk driver for NTI USB-SUN adapter

On Feb 01 2017 or thereabouts, Jonathan Tomer wrote: > These adapters allow pre-USB Sun keyboards to be connected to USB-only > machines, but include the wrong maximum keycode in their report > descriptor, making most of the keys present on Sun keyboards but not > 101-key PC keyboards

Re: [PATCH v2] HID: Add quirk driver for NTI USB-SUN adapter

On Feb 01 2017 or thereabouts, Jonathan Tomer wrote: > These adapters allow pre-USB Sun keyboards to be connected to USB-only > machines, but include the wrong maximum keycode in their report > descriptor, making most of the keys present on Sun keyboards but not > 101-key PC keyboards

RE: [PATCH 1/3] arc: vdk: Disable halt on reset

Hi Vineet, > -Original Message- > From: Vineet Gupta [mailto:vgu...@synopsys.com] > Sent: Wednesday, February 1, 2017 10:56 PM > To: Alexey Brodkin > Cc: Ruud Derwig ; linux-kernel@vger.kernel.org; > linux-snps-...@lists.infradead.org >

RE: [PATCH 1/3] arc: vdk: Disable halt on reset

Hi Vineet, > -Original Message- > From: Vineet Gupta [mailto:vgu...@synopsys.com] > Sent: Wednesday, February 1, 2017 10:56 PM > To: Alexey Brodkin > Cc: Ruud Derwig ; linux-kernel@vger.kernel.org; > linux-snps-...@lists.infradead.org > Subject: Re: [PATCH 1/3] arc: vdk: Disable halt on

[RFC PATCH] x86/CPU/AMD: Bring back Compute Unit ID

From: Borislav Petkov a33d331761bc ("x86/CPU/AMD: Fix Bulldozer topology") restored the initial approach we had with the Fam15h topology of enumerating CU (Compute Unit) threads as cores. And this is still correct - they're beefier than HT threads but still have some shared

[RFC PATCH] x86/CPU/AMD: Bring back Compute Unit ID

From: Borislav Petkov a33d331761bc ("x86/CPU/AMD: Fix Bulldozer topology") restored the initial approach we had with the Fam15h topology of enumerating CU (Compute Unit) threads as cores. And this is still correct - they're beefier than HT threads but still have some shared functionality. Our

Re: [PATCH v4 00/15] livepatch: hybrid consistency model

On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote: > Here's v4, based on linux-next/master. Mostly minor changes this time, > primarily due to Petr's v3 comments. So far, the only review comments have been related to the first patch, of which I just posted an updated version. If

Re: [PATCH v4 00/15] livepatch: hybrid consistency model

On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote: > Here's v4, based on linux-next/master. Mostly minor changes this time, > primarily due to Petr's v3 comments. So far, the only review comments have been related to the first patch, of which I just posted an updated version. If

<    1   2   3   4   5   6   7   8   9   10   >