Re: [PATCH 2/2] MAINTAINERS: Add entry for device DAX

On Wed, Oct 18, 2017 at 8:40 AM, Ross Zwisler wrote: > And update the entry for filesystem DAX to differentiate them. > > Signed-off-by: Ross Zwisler > --- > MAINTAINERS | 8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) >

Re: [PATCH 2/2] MAINTAINERS: Add entry for device DAX

On Wed, Oct 18, 2017 at 8:40 AM, Ross Zwisler wrote: > And update the entry for filesystem DAX to differentiate them. > > Signed-off-by: Ross Zwisler > --- > MAINTAINERS | 8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index

RE: [PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in dql_complete()

From: Ard Biesheuvel > Sent: 18 October 2017 16:45 > Even though calling dql_completed() with a count that exceeds the > queued count is a serious error, it still does not justify bringing > down the entire kernel with a BUG_ON(). So relax it to a WARN_ON() > instead. > > Signed-off-by: Ard

RE: [PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in dql_complete()

From: Ard Biesheuvel > Sent: 18 October 2017 16:45 > Even though calling dql_completed() with a count that exceeds the > queued count is a serious error, it still does not justify bringing > down the entire kernel with a BUG_ON(). So relax it to a WARN_ON() > instead. > > Signed-off-by: Ard

Re: [PATCH 0/4] char-TPM: Adjustments for ten function implementations

On Wed, 2017-10-18 at 18:10 +0300, Jarkko Sakkinen wrote: > On Tue, Oct 17, 2017 at 08:57:13AM -0700, James Bottomley wrote: > > > > On Tue, 2017-10-17 at 11:25 +0200, SF Markus Elfring wrote: > > > > > > > > > > > > > > > Fixes is only for bug fixes.  These don't fix any bugs. > > > > > >

Re: [PATCH 0/4] char-TPM: Adjustments for ten function implementations

On Wed, 2017-10-18 at 18:10 +0300, Jarkko Sakkinen wrote: > On Tue, Oct 17, 2017 at 08:57:13AM -0700, James Bottomley wrote: > > > > On Tue, 2017-10-17 at 11:25 +0200, SF Markus Elfring wrote: > > > > > > > > > > > > > > > Fixes is only for bug fixes.  These don't fix any bugs. > > > > > >

[PATCH 0/2] rt5651: Enable platforms with int mic on IN2

From: Carlo Caione While working on enabling a cherry-trail laptop shipping the rt5651 codec I realized that the machine driver needed some fixup. In particular the laptop I'm working on (KIANO SlimNote 14.2) has the internal mic connected to the IN2 port. All the

[PATCH 2/2] ASoC: intel: byt: Introduce new custom IN2 map

From: Carlo Caione Introduce a new custom dapm routes map to quirk platforms with the internal mic connected to IN2P. Signed-off-by: Carlo Caione --- sound/soc/intel/boards/bytcr_rt5651.c | 15 ++- 1 file changed, 14 insertions(+), 1

[PATCH 2/2] ASoC: intel: byt: Introduce new custom IN2 map

From: Carlo Caione Introduce a new custom dapm routes map to quirk platforms with the internal mic connected to IN2P. Signed-off-by: Carlo Caione --- sound/soc/intel/boards/bytcr_rt5651.c | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git

[PATCH 0/2] rt5651: Enable platforms with int mic on IN2

From: Carlo Caione While working on enabling a cherry-trail laptop shipping the rt5651 codec I realized that the machine driver needed some fixup. In particular the laptop I'm working on (KIANO SlimNote 14.2) has the internal mic connected to the IN2 port. All the laptop-specific work with the

[PATCH 1/2] ASoC: intel: byt: Enable quirk logic for custom maps

From: Carlo Caione Enable again the quirk logic for the custom dapm routes. Signed-off-by: Carlo Caione --- sound/soc/intel/boards/bytcr_rt5651.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/sound/soc/intel/boards/bytcr_rt5651.c

Re: [PATCH v2] static_key: Improve uninizialized key warning

On Wed, 18 Oct 2017 12:06:59 -0400 Steven Rostedt wrote: > > Signed-off-by: Borislav Petkov > > Cc: Hannes Frederic Sowa > > Cc: Ingo Molnar > > Cc: Juergen Gross > > Cc: "Steven Rostedt

[PATCH 1/2] ASoC: intel: byt: Enable quirk logic for custom maps

From: Carlo Caione Enable again the quirk logic for the custom dapm routes. Signed-off-by: Carlo Caione --- sound/soc/intel/boards/bytcr_rt5651.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/sound/soc/intel/boards/bytcr_rt5651.c b/sound/soc/intel/boards/bytcr_rt5651.c index

Re: [PATCH v2] static_key: Improve uninizialized key warning

On Wed, 18 Oct 2017 12:06:59 -0400 Steven Rostedt wrote: > > Signed-off-by: Borislav Petkov > > Cc: Hannes Frederic Sowa > > Cc: Ingo Molnar > > Cc: Juergen Gross > > Cc: "Steven Rostedt (VMware)" > > Reviewed-by: Steven Rostedt (VMware) > Ingo, you may want to fix the typo in the

Re: [PATCH v2] static_key: Improve uninizialized key warning

On Wed, 18 Oct 2017 17:24:28 +0200 Borislav Petkov wrote: > On Wed, Oct 18, 2017 at 09:27:10AM -0400, Steven Rostedt wrote: > > Boris, can you try it with "%pS" ? > > %ps is better, as it doesn't dump offsets: Sometimes offsets are helpful even for variables. But

Re: [PATCH v2] static_key: Improve uninizialized key warning

On Wed, 18 Oct 2017 17:24:28 +0200 Borislav Petkov wrote: > On Wed, Oct 18, 2017 at 09:27:10AM -0400, Steven Rostedt wrote: > > Boris, can you try it with "%pS" ? > > %ps is better, as it doesn't dump offsets: Sometimes offsets are helpful even for variables. But regardless... > > [

[PATCH v2] vfs: Improve overflow checking for stat*() compat fields

The checks for overflown fields in compat_statfs[64] structures are heuristic and are not error prone. This patch introduces ASSIGN_CHECK_OVERFLOW() family of macros which assign a field from a kernel representation and check if value is get truncated or changed its sign if the types of compat and

[PATCH v2] vfs: Improve overflow checking for stat*() compat fields

The checks for overflown fields in compat_statfs[64] structures are heuristic and are not error prone. This patch introduces ASSIGN_CHECK_OVERFLOW() family of macros which assign a field from a kernel representation and check if value is get truncated or changed its sign if the types of compat and

Re: [PATCH v2 02/15] usb: gadget: make config_item_type structures const

Hi Bhumika, Thank you for the patch. On Monday, 16 October 2017 18:18:41 EEST Bhumika Goyal wrote: > Make these structures const as they are only passed to the const > argument of the functions config_{group/item}_init_type_name. > > Signed-off-by: Bhumika Goyal > --- > *

Re: linux-next: manual merge of the usb-gadget tree with the usb tree

On Wed, Oct 18, 2017 at 08:40:04AM -0700, Kees Cook wrote: > On Wed, Oct 18, 2017 at 7:49 AM, Mark Brown wrote: > > I fixed it up with the USB version and can carry the fix as necessary. This > > is now fixed as far as linux-next is concerned, but any non trivial > >

Re: [PATCH v2 02/15] usb: gadget: make config_item_type structures const

Hi Bhumika, Thank you for the patch. On Monday, 16 October 2017 18:18:41 EEST Bhumika Goyal wrote: > Make these structures const as they are only passed to the const > argument of the functions config_{group/item}_init_type_name. > > Signed-off-by: Bhumika Goyal > --- > * Changes in v2-

Re: linux-next: manual merge of the usb-gadget tree with the usb tree

On Wed, Oct 18, 2017 at 08:40:04AM -0700, Kees Cook wrote: > On Wed, Oct 18, 2017 at 7:49 AM, Mark Brown wrote: > > I fixed it up with the USB version and can carry the fix as necessary. This > > is now fixed as far as linux-next is concerned, but any non trivial > > conflicts should be

Re: rcu kernel-doc issues (4.14-rc1)

On Mon, 16 Oct 2017 13:26:19 -0700 "Paul E. McKenney" wrote: > OK, how about if I submit them to the 4.15 merge window, but add the > appropriate -stable tags to get them backported? Yes, these are bugs, > but I cannot in good conscience claim that they are v4.14

Re: rcu kernel-doc issues (4.14-rc1)

On Mon, 16 Oct 2017 13:26:19 -0700 "Paul E. McKenney" wrote: > OK, how about if I submit them to the 4.15 merge window, but add the > appropriate -stable tags to get them backported? Yes, these are bugs, > but I cannot in good conscience claim that they are v4.14 regressions. > > But if Jon

Re: [PATCH v5 8/9] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

On 18/10/2017 14:09, Jeffy Chen wrote: > Let plat drivers own the drvdata, so that they could cleanup resources > in their unbind(). > > Signed-off-by: Jeffy Chen > --- > > Changes in v5: None > > drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43 >

Re: [PATCH v5 8/9] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

On 18/10/2017 14:09, Jeffy Chen wrote: > Let plat drivers own the drvdata, so that they could cleanup resources > in their unbind(). > > Signed-off-by: Jeffy Chen > --- > > Changes in v5: None > > drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43 > ++--- >

Re: [PATCH 1/2] mm, thp: introduce dedicated transparent huge page allocation interfaces

-dedicated-transparent-huge-page-allocation-interfaces/20171018-230128 base: git://git.cmpxchg.org/linux-mmotm.git master config: i386-randconfig-x001-201742 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree

Re: [PATCH 1/2] mm, thp: introduce dedicated transparent huge page allocation interfaces

-dedicated-transparent-huge-page-allocation-interfaces/20171018-230128 base: git://git.cmpxchg.org/linux-mmotm.git master config: i386-randconfig-x001-201742 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree

[PATCH 1/1] net: ethtool: add support for reset of AP inside NIC interface.

Add ETH_RESET_AP to reset the application processor inside the NIC interface. Signed-off-by: Scott Branden --- include/uapi/linux/ethtool.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/linux/ethtool.h b/include/uapi/linux/ethtool.h index

[PATCH 1/1] net: ethtool: add support for reset of AP inside NIC interface.

Add ETH_RESET_AP to reset the application processor inside the NIC interface. Signed-off-by: Scott Branden --- include/uapi/linux/ethtool.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/linux/ethtool.h b/include/uapi/linux/ethtool.h index 5bd1b1d..f927ab7 100644 ---

[PATCH 0/1] net: ethtool: add SmartNIC reset support

Ethtool provides support for resetting other internal portions of the NIC already. Seems appropriate to use one of the bits for resetting the application processor (AP) for SmartNICs. If we are not able to use ethtool to reset such portions of the NIC we will need to create some other API that

[PATCH 0/1] net: ethtool: add SmartNIC reset support

Ethtool provides support for resetting other internal portions of the NIC already. Seems appropriate to use one of the bits for resetting the application processor (AP) for SmartNICs. If we are not able to use ethtool to reset such portions of the NIC we will need to create some other API that

Re: char/tpm: Improve a size determination in nine functions

On Wed, Oct 18, 2017 at 05:22:19PM +0200, SF Markus Elfring wrote: > >> Do you find my wording “This issue was detected by using the > >> Coccinelle software.” insufficient? > > > > This is fine for cover letter, not for the commits. > > I guess that there are more opinions available by other

Re: char/tpm: Improve a size determination in nine functions

On Wed, Oct 18, 2017 at 05:22:19PM +0200, SF Markus Elfring wrote: > >> Do you find my wording “This issue was detected by using the > >> Coccinelle software.” insufficient? > > > > This is fine for cover letter, not for the commits. > > I guess that there are more opinions available by other

dtc issue with overlays starting in next-20171009

Hi Rob, I've noticed a problem compiling DT overlays and traced it back to beginning in next-20171009 That tag adds the following in scripts/dtc e9480c1 2017-10-09 16:17:32 +0100 : Mark Brown : Merge remote-tracking branch 'devicetree/for-next' 4201d05 2017-10-03 15:03:47 -0500 : Rob Herring :

dtc issue with overlays starting in next-20171009

Hi Rob, I've noticed a problem compiling DT overlays and traced it back to beginning in next-20171009 That tag adds the following in scripts/dtc e9480c1 2017-10-09 16:17:32 +0100 : Mark Brown : Merge remote-tracking branch 'devicetree/for-next' 4201d05 2017-10-03 15:03:47 -0500 : Rob Herring :

[GIT PULL] tpmdd updates for Linux 4.15

in tpm_tis_spi. /Jarkko The following changes since commit 25eabb13c7d67ae32298015c5e28d00f604f412c: Merge tag 'v4.14-rc2' into next-general (2017-09-24 22:41:55 -0700) are available in the git repository at: git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20171018

[GIT PULL] tpmdd updates for Linux 4.15

in tpm_tis_spi. /Jarkko The following changes since commit 25eabb13c7d67ae32298015c5e28d00f604f412c: Merge tag 'v4.14-rc2' into next-general (2017-09-24 22:41:55 -0700) are available in the git repository at: git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20171018

RE: [PATCH] RDMA/i40iw: Convert timers to use timer_setup() (part 2)

> Subject: [PATCH] RDMA/i40iw: Convert timers to use timer_setup() (part 2) > > In preparation for unconditionally passing the struct timer_list pointer to > all timer > callbacks, switch to using the new timer_setup() and from_timer() to pass the > timer > pointer explicitly. > > This

RE: [PATCH] RDMA/i40iw: Convert timers to use timer_setup() (part 2)

> Subject: [PATCH] RDMA/i40iw: Convert timers to use timer_setup() (part 2) > > In preparation for unconditionally passing the struct timer_list pointer to > all timer > callbacks, switch to using the new timer_setup() and from_timer() to pass the > timer > pointer explicitly. > > This

Re: [PATCH 1/2] dev/dax: fix uninitialized variable build warning

On Wed, Oct 18, 2017 at 8:40 AM, Ross Zwisler wrote: > Fix this build warning: > > warning: 'phys' may be used uninitialized in this function > [-Wuninitialized] > > As reported here: > > https://lkml.org/lkml/2017/10/16/152 > > This should have no functional change

Re: [PATCH 1/2] dev/dax: fix uninitialized variable build warning

On Wed, Oct 18, 2017 at 8:40 AM, Ross Zwisler wrote: > Fix this build warning: > > warning: 'phys' may be used uninitialized in this function > [-Wuninitialized] > > As reported here: > > https://lkml.org/lkml/2017/10/16/152 > > This should have no functional change because you can only get into

Re: [PATCH 1/2] mm, thp: introduce dedicated transparent huge page allocation interfaces

-dedicated-transparent-huge-page-allocation-interfaces/20171018-230128 base: git://git.cmpxchg.org/linux-mmotm.git master config: i386-randconfig-x003-201742 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree

Re: [PATCH 1/2] mm, thp: introduce dedicated transparent huge page allocation interfaces

-dedicated-transparent-huge-page-allocation-interfaces/20171018-230128 base: git://git.cmpxchg.org/linux-mmotm.git master config: i386-randconfig-x003-201742 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree

Re: [PATCH] IB/rdmavt: Convert timers to use timer_setup()

On Mon, 2017-10-16 at 15:51 -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list > pointer to > all timer callbacks, switch to using the new timer_setup() and > from_timer() > to pass the timer pointer explicitly. > > setup_timer() was already being called

Re: [PATCH] IB/rdmavt: Convert timers to use timer_setup()

On Mon, 2017-10-16 at 15:51 -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list > pointer to > all timer callbacks, switch to using the new timer_setup() and > from_timer() > to pass the timer pointer explicitly. > > setup_timer() was already being called

Re: [PATCH] thermal/drivers/hisi: disable multi alarm support for hi3660 SoC

On 18/10/2017 11:15, Tao Wang wrote: > From: Kevin Wangtao > > multi alarm interrupt forced a re-trigger of power_allocator_throttle > which changes the PID's actual sampling rate, this isn't optimal for > IPA, it is best to disable multi alarm support now and sort out

Re: [PATCH] thermal/drivers/hisi: disable multi alarm support for hi3660 SoC

On 18/10/2017 11:15, Tao Wang wrote: > From: Kevin Wangtao > > multi alarm interrupt forced a re-trigger of power_allocator_throttle > which changes the PID's actual sampling rate, this isn't optimal for > IPA, it is best to disable multi alarm support now and sort out this > issue later. > >

Re: libbattery was Re: [RFC PATCH 5/5] power: generic-adc-battery: Add capacity handling

> Am 18.10.2017 um 15:56 schrieb Pavel Machek : > > On Wed 2017-10-18 06:22:04, Tony Lindgren wrote: >> * H. Nikolaus Schaller [171018 05:49]: Am 18.10.2017 um 14:28 schrieb Pavel Machek : So I started something, it is at.

Re: libbattery was Re: [RFC PATCH 5/5] power: generic-adc-battery: Add capacity handling

> Am 18.10.2017 um 15:56 schrieb Pavel Machek : > > On Wed 2017-10-18 06:22:04, Tony Lindgren wrote: >> * H. Nikolaus Schaller [171018 05:49]: Am 18.10.2017 um 14:28 schrieb Pavel Machek : So I started something, it is at. https://github.com/pavelmachek/libbattery

Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver

On Wed, Oct 18, 2017 at 6:03 AM, Stefan Hajnoczi wrote: > On Tue, Oct 17, 2017 at 04:30:41AM -0400, Pankaj Gupta wrote: >> >> > > Are you saying do it as existing i.e ACPI pmem like interface? >> > > The reason we have created this new driver is exiting pmem driver >> > > does

Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver

On Wed, Oct 18, 2017 at 6:03 AM, Stefan Hajnoczi wrote: > On Tue, Oct 17, 2017 at 04:30:41AM -0400, Pankaj Gupta wrote: >> >> > > Are you saying do it as existing i.e ACPI pmem like interface? >> > > The reason we have created this new driver is exiting pmem driver >> > > does not define proper

Re: [PATCH] IB/hfi1: Convert timers to use timer_setup()

On Mon, 2017-10-16 at 15:51 -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list > pointer to > all timer callbacks, switch to using the new timer_setup() and > from_timer() > to pass the timer pointer explicitly. Switches test of .data field to > .function,

Re: [PATCH v2] watchdog: core: Make use of devm_register_reboot_notifier()

On Tue, Oct 17, 2017 at 3:08 PM, Andrew Morton wrote: > On Tue, 17 Oct 2017 08:50:12 -0700 Andrey Smirnov > wrote: > >> On Sat, Apr 15, 2017 at 11:11 PM, Guenter Roeck wrote: >> > On 04/11/2017 09:06 AM, Andrey Smirnov

Re: [PATCH] IB/hfi1: Convert timers to use timer_setup()

On Mon, 2017-10-16 at 15:51 -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list > pointer to > all timer callbacks, switch to using the new timer_setup() and > from_timer() > to pass the timer pointer explicitly. Switches test of .data field to > .function,

Re: [PATCH v2] watchdog: core: Make use of devm_register_reboot_notifier()

On Tue, Oct 17, 2017 at 3:08 PM, Andrew Morton wrote: > On Tue, 17 Oct 2017 08:50:12 -0700 Andrey Smirnov > wrote: > >> On Sat, Apr 15, 2017 at 11:11 PM, Guenter Roeck wrote: >> > On 04/11/2017 09:06 AM, Andrey Smirnov wrote: >> >> >> >> Save a bit of cleanup code by leveraging newly added >>

Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name

On Wed, 2017-10-18 at 10:44 -0500, Rob Herring wrote: > On Wed, Oct 18, 2017 at 10:12 AM, Alan Tull wrote: > > On Tue, Oct 17, 2017 at 6:51 PM, Frank Rowand > > wrote: > >> On 10/17/17 14:46, Rob Herring wrote: > >>> On Tue, Oct 17, 2017 at 4:32 PM,

Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name

On Wed, 2017-10-18 at 10:44 -0500, Rob Herring wrote: > On Wed, Oct 18, 2017 at 10:12 AM, Alan Tull wrote: > > On Tue, Oct 17, 2017 at 6:51 PM, Frank Rowand > > wrote: > >> On 10/17/17 14:46, Rob Herring wrote: > >>> On Tue, Oct 17, 2017 at 4:32 PM, Alan Tull wrote: > On Mon, Aug 21, 2017

Re: [PATCH 02/25] thermal/drivers/hisi: Remove the multiple sensors support

On Wed, Oct 18, 2017 at 09:48:21AM +0800, Leo Yan wrote: > On Tue, Oct 17, 2017 at 02:07:08PM -0700, Eduardo Valentin wrote: > > On Tue, Oct 17, 2017 at 09:03:40PM +0200, Daniel Lezcano wrote: > > > On 17/10/2017 20:25, Eduardo Valentin wrote: > > > > Hello, > > > > > > > > On Tue, Oct 17, 2017

Re: [PATCH 02/25] thermal/drivers/hisi: Remove the multiple sensors support

On Wed, Oct 18, 2017 at 09:48:21AM +0800, Leo Yan wrote: > On Tue, Oct 17, 2017 at 02:07:08PM -0700, Eduardo Valentin wrote: > > On Tue, Oct 17, 2017 at 09:03:40PM +0200, Daniel Lezcano wrote: > > > On 17/10/2017 20:25, Eduardo Valentin wrote: > > > > Hello, > > > > > > > > On Tue, Oct 17, 2017

Re: [PATCH] RDMA/i40iw: Convert timers to use timer_setup() (part 2)

On Tue, 2017-10-17 at 11:37 -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list > pointer to > all timer callbacks, switch to using the new timer_setup() and > from_timer() > to pass the timer pointer explicitly. > > This includes the remaining timers missed

Re: [PATCH] RDMA/i40iw: Convert timers to use timer_setup() (part 2)

On Tue, 2017-10-17 at 11:37 -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list > pointer to > all timer callbacks, switch to using the new timer_setup() and > from_timer() > to pass the timer pointer explicitly. > > This includes the remaining timers missed

Re: [PATCH] RDMA/cxgb3: Convert timers to use timer_setup()

On Tue, 2017-10-17 at 09:26 -0500, Steve Wise wrote: > > In preparation for unconditionally passing the struct timer_list > > pointer to > > all timer callbacks, switch to using the new timer_setup() and > > from_timer() > > to pass the timer pointer explicitly. Also removes an unused timer. > >

Re: [PATCH] RDMA/cxgb3: Convert timers to use timer_setup()

On Tue, 2017-10-17 at 09:26 -0500, Steve Wise wrote: > > In preparation for unconditionally passing the struct timer_list > > pointer to > > all timer callbacks, switch to using the new timer_setup() and > > from_timer() > > to pass the timer pointer explicitly. Also removes an unused timer. > >

[GIT PULL] tpmdd updates for Linux 4.15

in tpm_tis_spi. /Jarkko The following changes since commit 25eabb13c7d67ae32298015c5e28d00f604f412c: Merge tag 'v4.14-rc2' into next-general (2017-09-24 22:41:55 -0700) are available in the git repository at: git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20171018

[GIT PULL] tpmdd updates for Linux 4.15

in tpm_tis_spi. /Jarkko The following changes since commit 25eabb13c7d67ae32298015c5e28d00f604f412c: Merge tag 'v4.14-rc2' into next-general (2017-09-24 22:41:55 -0700) are available in the git repository at: git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20171018

Re: libbattery was Re: [RFC PATCH 5/5] power: generic-adc-battery: Add capacity handling

> Am 18.10.2017 um 15:22 schrieb Tony Lindgren : > > * H. Nikolaus Schaller [171018 05:49]: >>> Am 18.10.2017 um 14:28 schrieb Pavel Machek : >>> >>> So I started something, it is at. >>> >>> https://github.com/pavelmachek/libbattery >>>

Re: libbattery was Re: [RFC PATCH 5/5] power: generic-adc-battery: Add capacity handling

> Am 18.10.2017 um 15:22 schrieb Tony Lindgren : > > * H. Nikolaus Schaller [171018 05:49]: >>> Am 18.10.2017 um 14:28 schrieb Pavel Machek : >>> >>> So I started something, it is at. >>> >>> https://github.com/pavelmachek/libbattery >>> >>> My battery on n900 is currently uncalibrated (and

Re: [PATCH 3/3] irq/irq_sim: implement irq_sim_irq2offset()

On Wed, Oct 18 2017 at 2:49:07 pm BST, Bartosz Golaszewski wrote: > 2017-10-18 12:13 GMT+02:00 Marc Zyngier : >> > > [snip!] > >> It looks to me that this is all because the irq_sim creation is a bit >> awkward. >> You end-up with all kind of exotic

Re: [PATCH 3/3] irq/irq_sim: implement irq_sim_irq2offset()

On Wed, Oct 18 2017 at 2:49:07 pm BST, Bartosz Golaszewski wrote: > 2017-10-18 12:13 GMT+02:00 Marc Zyngier : >> > > [snip!] > >> It looks to me that this is all because the irq_sim creation is a bit >> awkward. >> You end-up with all kind of exotic interfaces because you don't know the base

Re: [RFC PATCH 1/4] dt-bindings: add bindings for USB physical connector

Hi Andrzej, On Wednesday, 18 October 2017 18:11:25 EEST Laurent Pinchart wrote: > On Thursday, 28 September 2017 16:07:27 EEST Andrzej Hajda wrote: > > These bindings allows to describe most known standard USB connectors > > and it should be possible to extend it if necessary. > > USB connectors,

Re: [RFC PATCH 1/4] dt-bindings: add bindings for USB physical connector

Hi Andrzej, On Wednesday, 18 October 2017 18:11:25 EEST Laurent Pinchart wrote: > On Thursday, 28 September 2017 16:07:27 EEST Andrzej Hajda wrote: > > These bindings allows to describe most known standard USB connectors > > and it should be possible to extend it if necessary. > > USB connectors,

[PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in dql_complete()

Even though calling dql_completed() with a count that exceeds the queued count is a serious error, it still does not justify bringing down the entire kernel with a BUG_ON(). So relax it to a WARN_ON() instead. Signed-off-by: Ard Biesheuvel ---

[PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in dql_complete()

Even though calling dql_completed() with a count that exceeds the queued count is a serious error, it still does not justify bringing down the entire kernel with a BUG_ON(). So relax it to a WARN_ON() instead. Signed-off-by: Ard Biesheuvel --- lib/dynamic_queue_limits.c | 2 +- 1 file changed,

Re: [PATCH v7 7/6] fs/epoll: scale nested callbacks

On Wed, 18 Oct 2017, Jason Baron wrote: If there are not many EPOLL_CTL_ADDs, then I wouldn't think loop_ncalls would be highly contented (since it should only be called from the add path)? So yeah it's all about the readywalks. Thanks, Davidlohr

Re: [PATCH v7 7/6] fs/epoll: scale nested callbacks

On Wed, 18 Oct 2017, Jason Baron wrote: If there are not many EPOLL_CTL_ADDs, then I wouldn't think loop_ncalls would be highly contented (since it should only be called from the add path)? So yeah it's all about the readywalks. Thanks, Davidlohr

Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name

On Wed, Oct 18, 2017 at 10:12 AM, Alan Tull wrote: > On Tue, Oct 17, 2017 at 6:51 PM, Frank Rowand wrote: >> On 10/17/17 14:46, Rob Herring wrote: >>> On Tue, Oct 17, 2017 at 4:32 PM, Alan Tull wrote: On Mon, Aug 21, 2017 at 10:16

Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name

On Wed, Oct 18, 2017 at 10:12 AM, Alan Tull wrote: > On Tue, Oct 17, 2017 at 6:51 PM, Frank Rowand wrote: >> On 10/17/17 14:46, Rob Herring wrote: >>> On Tue, Oct 17, 2017 at 4:32 PM, Alan Tull wrote: On Mon, Aug 21, 2017 at 10:16 AM, Rob Herring wrote: Hi Rob, > With

Re: char-TPM: Adjustments for ten function implementations

>>> A minor complaint: all commits are missing "Fixes:" tag. >> >> * Do you require it to be added to the commit messages? > > I don't require it. It's part of the development process: > > https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html Yes. - But other contributors

Re: char-TPM: Adjustments for ten function implementations

>>> A minor complaint: all commits are missing "Fixes:" tag. >> >> * Do you require it to be added to the commit messages? > > I don't require it. It's part of the development process: > > https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html Yes. - But other contributors

Re: [PATCH V2 4/5] perf record: synthesize event multithreading support

On Wed, Oct 18, 2017 at 07:29:32AM -0700, kan.li...@intel.com wrote: SNIP > + rec->synthesized_file = calloc(nr_thread, sizeof(struct > perf_data_file)); > + if (rec->synthesized_file == NULL) { > + pr_debug("Could not do multithread synthesize." > +

Re: [PATCH V2 4/5] perf record: synthesize event multithreading support

On Wed, Oct 18, 2017 at 07:29:32AM -0700, kan.li...@intel.com wrote: SNIP > + rec->synthesized_file = calloc(nr_thread, sizeof(struct > perf_data_file)); > + if (rec->synthesized_file == NULL) { > + pr_debug("Could not do multithread synthesize." > +

Re: [for-next][PATCH 1/7] tracing, dma-buf: Remove unused trace event dma_fence_annotate_wait_on

On Wed, 18 Oct 2017 09:28:08 -0400 Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > Commit e941759c74 ("fence: dma-buf cross-device synchronization") added > trace event fence_annotate_wait_on, but never used it. It was renamed > to

Re: [for-next][PATCH 1/7] tracing, dma-buf: Remove unused trace event dma_fence_annotate_wait_on

On Wed, 18 Oct 2017 09:28:08 -0400 Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > Commit e941759c74 ("fence: dma-buf cross-device synchronization") added > trace event fence_annotate_wait_on, but never used it. It was renamed > to dma_fence_annotate_wait_on by commit f54d186700

Request for O_CLOFORK, akin to O_CLOEXEC.

Hi, Please keep me CC'd. A multi-threaded program's thread A wants to create a new executable file with open(O_CLOEXEC), write, close, and then fork and exec it. Meanwhile, another thread B forks before A's close, carrying a reference to the open file description with it, thus A's execve fails

Request for O_CLOFORK, akin to O_CLOEXEC.

Hi, Please keep me CC'd. A multi-threaded program's thread A wants to create a new executable file with open(O_CLOEXEC), write, close, and then fork and exec it. Meanwhile, another thread B forks before A's close, carrying a reference to the open file description with it, thus A's execve fails

Re: [PATCH] rcu: do not include rtmutex_common.h unconditionally

On Wed, Oct 18, 2017 at 10:34:36AM +0200, Sebastian Andrzej Siewior wrote: > Since commit bcda31a26594 ("rcu: Suppress lockdep false-positive > ->boost_mtx complaints") the rtmutex_common.h is included > unconditionally. This break CONFIG_FUTEX=n configs which do not have > CONFIG_RT_MUTEX enabled

Re: [PATCH] rcu: do not include rtmutex_common.h unconditionally

On Wed, Oct 18, 2017 at 10:34:36AM +0200, Sebastian Andrzej Siewior wrote: > Since commit bcda31a26594 ("rcu: Suppress lockdep false-positive > ->boost_mtx complaints") the rtmutex_common.h is included > unconditionally. This break CONFIG_FUTEX=n configs which do not have > CONFIG_RT_MUTEX enabled

Re: Changing the ARM variant reported by 'uname -m'

Hi Tuomas, On Wed, Oct 18, 2017 at 06:07:22PM +0300, Tuomas Tynkkynen wrote: > Hi, > > For our distro (NixOS), I've experimented with building packages for ARMv6 > on ARMv7 hardware. This has generally worked fine, except that some build > scripts (in coreutils, for example) notice that `uname

[PATCH 2/2] MAINTAINERS: Add entry for device DAX

And update the entry for filesystem DAX to differentiate them. Signed-off-by: Ross Zwisler --- MAINTAINERS | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index a74227a..b2b2e75 100644 --- a/MAINTAINERS +++

Re: Changing the ARM variant reported by 'uname -m'

Hi Tuomas, On Wed, Oct 18, 2017 at 06:07:22PM +0300, Tuomas Tynkkynen wrote: > Hi, > > For our distro (NixOS), I've experimented with building packages for ARMv6 > on ARMv7 hardware. This has generally worked fine, except that some build > scripts (in coreutils, for example) notice that `uname

[PATCH 2/2] MAINTAINERS: Add entry for device DAX

And update the entry for filesystem DAX to differentiate them. Signed-off-by: Ross Zwisler --- MAINTAINERS | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index a74227a..b2b2e75 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -4162,7 +4162,7 @@

Re: linux-next: manual merge of the usb-gadget tree with the usb tree

On Wed, Oct 18, 2017 at 7:42 AM, Mark Brown wrote: > Hi Felipe, > > Today's linux-next merge of the usb-gadget tree got a conflict in: > > drivers/usb/gadget/udc/snps_udc_core.c > > between commit: > > 29bce57723351f63d ("usb/gadget/snps_udc_core: Convert timers to use >

Re: linux-next: manual merge of the usb-gadget tree with the usb tree

On Wed, Oct 18, 2017 at 7:42 AM, Mark Brown wrote: > Hi Felipe, > > Today's linux-next merge of the usb-gadget tree got a conflict in: > > drivers/usb/gadget/udc/snps_udc_core.c > > between commit: > > 29bce57723351f63d ("usb/gadget/snps_udc_core: Convert timers to use > timer_setup()") > >

Re: [PATCH v3 2/2] KVM: VMX: Fix VPID capability detection

On 18/10/2017 17:39, Jim Mattson wrote: > As long as we're taking the "better safe than sorry" approach, why > don't we go ahead and clear vmx_capability.ept/vmx_capability.vpid > along with the warnings? Indeed. Paolo > On Tue, Oct 17, 2017 at 6:43 PM, Wanpeng Li wrote:

Re: [PATCH v3 2/2] KVM: VMX: Fix VPID capability detection

On 18/10/2017 17:39, Jim Mattson wrote: > As long as we're taking the "better safe than sorry" approach, why > don't we go ahead and clear vmx_capability.ept/vmx_capability.vpid > along with the warnings? Indeed. Paolo > On Tue, Oct 17, 2017 at 6:43 PM, Wanpeng Li wrote: >> From: Wanpeng Li

Re: linux-next: manual merge of the usb-gadget tree with the usb tree

On Wed, Oct 18, 2017 at 7:49 AM, Mark Brown wrote: > Hi Felipe, > > Today's linux-next merge of the usb-gadget tree got a conflict in: > > drivers/usb/phy/phy-isp1301-omap.c > > between commit: > > 4c13fec1ba55595 ("usb: isp1301-omap: Convert timers to use timer_setup()")

Re: linux-next: manual merge of the usb-gadget tree with the usb tree

On Wed, Oct 18, 2017 at 7:49 AM, Mark Brown wrote: > Hi Felipe, > > Today's linux-next merge of the usb-gadget tree got a conflict in: > > drivers/usb/phy/phy-isp1301-omap.c > > between commit: > > 4c13fec1ba55595 ("usb: isp1301-omap: Convert timers to use timer_setup()") > > from the usb

[PATCH 1/2] dev/dax: fix uninitialized variable build warning

Fix this build warning: warning: 'phys' may be used uninitialized in this function [-Wuninitialized] As reported here: https://lkml.org/lkml/2017/10/16/152 This should have no functional change because you can only get into the if statement in dax_pgoff_to_phys() that is complaining about

[PATCH 1/2] dev/dax: fix uninitialized variable build warning

Fix this build warning: warning: 'phys' may be used uninitialized in this function [-Wuninitialized] As reported here: https://lkml.org/lkml/2017/10/16/152 This should have no functional change because you can only get into the if statement in dax_pgoff_to_phys() that is complaining about

<    5   6   7   8   9   10   11   12   13   14   >