Re: [PATCH v2 08/11] block: sed-opal: ioctl for writing to shadow mbr

On Thu, Mar 29, 2018 at 07:30:02PM +0200, Jonas Rabenstein wrote: > Hi, > On Wed, Mar 21, 2018 at 02:43:21AM +0100, Jonas Rabenstein wrote: > > On Tue, Mar 20, 2018 at 04:09:08PM -0600, Scott Bauer wrote: > > > On Tue, Mar 20, 2018 at 10:36:04AM +0100, Jonas Rabenstein wrote: > > > > On Mon, Mar

Re: [PATCH v2 08/11] block: sed-opal: ioctl for writing to shadow mbr

On Thu, Mar 29, 2018 at 07:30:02PM +0200, Jonas Rabenstein wrote: > Hi, > On Wed, Mar 21, 2018 at 02:43:21AM +0100, Jonas Rabenstein wrote: > > On Tue, Mar 20, 2018 at 04:09:08PM -0600, Scott Bauer wrote: > > > On Tue, Mar 20, 2018 at 10:36:04AM +0100, Jonas Rabenstein wrote: > > > > On Mon, Mar

Re: Problem with commit 31e77c93e432 "sched/fair: Update blocked load when newly idle"

Am 29.03.2018 um 09:41 schrieb Vincent Guittot: > On 28 March 2018 at 16:01, Vincent Guittot wrote: >> Hi, >> >> On 28 March 2018 at 12:37, Dietmar Eggemann wrote: >>> Hi, >>> >>> On 03/24/2018 01:47 PM, Heiner Kallweit wrote: Am

Re: [PATCH 8/8] fs/aio: Use rcu_work instead of explicit rcu and work item

Hello, On Thu, Mar 29, 2018 at 06:49:25PM +0200, Oleg Nesterov wrote: > Still no use-case... But yes, I forgot this is needed for correctness. > > OK, thanks for your patience. But fyi now I hate this interface even more, > exactly because I was technically wrong in this discussion ;) Yeah, we

Re: Problem with commit 31e77c93e432 "sched/fair: Update blocked load when newly idle"

Am 29.03.2018 um 09:41 schrieb Vincent Guittot: > On 28 March 2018 at 16:01, Vincent Guittot wrote: >> Hi, >> >> On 28 March 2018 at 12:37, Dietmar Eggemann wrote: >>> Hi, >>> >>> On 03/24/2018 01:47 PM, Heiner Kallweit wrote: Am 24.03.2018 um 07:46 schrieb Vincent Guittot: > >

Re: [PATCH 8/8] fs/aio: Use rcu_work instead of explicit rcu and work item

Hello, On Thu, Mar 29, 2018 at 06:49:25PM +0200, Oleg Nesterov wrote: > Still no use-case... But yes, I forgot this is needed for correctness. > > OK, thanks for your patience. But fyi now I hate this interface even more, > exactly because I was technically wrong in this discussion ;) Yeah, we

Re: [PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

On 3/29/2018 10:02 AM, Logan Gunthorpe wrote: Per the bug in the previous patch, I don't think that was ever a valid assumption. It doesn't have anything to do with the sgl_alloc change either. The dma_map interface is allowed to merge SGLs and that's why it can return fewer nents than it was

Re: [PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

On 3/29/2018 10:02 AM, Logan Gunthorpe wrote: Per the bug in the previous patch, I don't think that was ever a valid assumption. It doesn't have anything to do with the sgl_alloc change either. The dma_map interface is allowed to merge SGLs and that's why it can return fewer nents than it was

Re: [PATCH v2 04/21] kconfig: reference environments directly and remove 'option env=' syntax

On Thu, Mar 29, 2018 at 4:56 AM, Ulf Magnusson wrote: > On Thu, Mar 29, 2018 at 4:19 AM, Ulf Magnusson wrote: >> I've been kinda busy lately, so that's why I disappeared. >> >> I'll try to go over this patchset in more detail over the weekend. >> >> On

Re: [PATCH v2 04/21] kconfig: reference environments directly and remove 'option env=' syntax

On Thu, Mar 29, 2018 at 4:56 AM, Ulf Magnusson wrote: > On Thu, Mar 29, 2018 at 4:19 AM, Ulf Magnusson wrote: >> I've been kinda busy lately, so that's why I disappeared. >> >> I'll try to go over this patchset in more detail over the weekend. >> >> On Tue, Mar 27, 2018 at 7:29 AM, Masahiro

Re: [PATCH] of_net: Implement of_get_nvmem_mac_address helper

On 25-03-18 10:17, Mike Looijmans wrote: On 24-03-18 19:53, Andrew Lunn wrote: A quick survey for the of_get_mac_address users learns that most of them do a memcpy (or similar) right after it, so for these drivers the "of_get_nvmem_mac_address" style signature that performs the memcpy (or

Re: [PATCH] of_net: Implement of_get_nvmem_mac_address helper

On 25-03-18 10:17, Mike Looijmans wrote: On 24-03-18 19:53, Andrew Lunn wrote: A quick survey for the of_get_mac_address users learns that most of them do a memcpy (or similar) right after it, so for these drivers the "of_get_nvmem_mac_address" style signature that performs the memcpy (or

Re: [PATCH] selftests/ftrace: fix spelling mistake: "tiggers" -> "triggers"

On Thu, 29 Mar 2018 18:24:31 +0100 Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in message text > > Signed-off-by: Colin Ian King > --- >

Re: [PATCH] selftests/ftrace: fix spelling mistake: "tiggers" -> "triggers"

On Thu, 29 Mar 2018 18:24:31 +0100 Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in message text > > Signed-off-by: Colin Ian King > --- > tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH v2 08/11] block: sed-opal: ioctl for writing to shadow mbr

Hi, On Wed, Mar 21, 2018 at 02:43:21AM +0100, Jonas Rabenstein wrote: > On Tue, Mar 20, 2018 at 04:09:08PM -0600, Scott Bauer wrote: > > On Tue, Mar 20, 2018 at 10:36:04AM +0100, Jonas Rabenstein wrote: > > > On Mon, Mar 19, 2018 at 08:52:24PM +0100, Christoph Hellwig wrote: > > > > On Mon, Mar

Re: [PATCH v2 08/11] block: sed-opal: ioctl for writing to shadow mbr

Hi, On Wed, Mar 21, 2018 at 02:43:21AM +0100, Jonas Rabenstein wrote: > On Tue, Mar 20, 2018 at 04:09:08PM -0600, Scott Bauer wrote: > > On Tue, Mar 20, 2018 at 10:36:04AM +0100, Jonas Rabenstein wrote: > > > On Mon, Mar 19, 2018 at 08:52:24PM +0100, Christoph Hellwig wrote: > > > > On Mon, Mar

Re: [PATCH v4 2/7] phy: qcom-qmp: Enable pipe_clk before PHY initialization

Hi Manu, On Thu, Mar 29, 2018 at 4:06 AM Manu Gautam wrote: > QMP PHY for USB/PCIE requires pipe_clk for locking of > retime buffers at the pipe interface. Driver checks for > PHY_STATUS without enabling pipe_clk due to which > phy_init() fails with initialization

Re: [PATCH v4 2/7] phy: qcom-qmp: Enable pipe_clk before PHY initialization

Hi Manu, On Thu, Mar 29, 2018 at 4:06 AM Manu Gautam wrote: > QMP PHY for USB/PCIE requires pipe_clk for locking of > retime buffers at the pipe interface. Driver checks for > PHY_STATUS without enabling pipe_clk due to which > phy_init() fails with initialization timeout. > Though pipe_clk is

Re: [linux-sunxi] [PATCH v9 0/2] Initial Allwinner V3s CSI Support

On 03/28/2018 06:02 PM, Yong wrote: AFAIK, there is no document about MIPI CSI-2. You can take a look at the source code in BSP: https://github.com/friendlyarm/h3_lichee/tree/master/linux-3.4/drivers/media/video/sunxi-vfe/mipi_csi And try to port it to mainline. Yep, I see there's lots of

Re: [linux-sunxi] [PATCH v9 0/2] Initial Allwinner V3s CSI Support

On 03/28/2018 06:02 PM, Yong wrote: AFAIK, there is no document about MIPI CSI-2. You can take a look at the source code in BSP: https://github.com/friendlyarm/h3_lichee/tree/master/linux-3.4/drivers/media/video/sunxi-vfe/mipi_csi And try to port it to mainline. Yep, I see there's lots of

[PATCH] selftests/ftrace: fix spelling mistake: "tiggers" -> "triggers"

From: Colin Ian King Trivial fix to spelling mistake in message text Signed-off-by: Colin Ian King --- tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] selftests/ftrace: fix spelling mistake: "tiggers" -> "triggers"

From: Colin Ian King Trivial fix to spelling mistake in message text Signed-off-by: Colin Ian King --- tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 4/6] fpga: region: change fpga_region_register to have one param

On Thu, Mar 29, 2018 at 08:36:56AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_region_register to only take one parameter: > > int fpga_region_register(struct fpga_region *region) > > The parent dev is added to struct fpga_region. > > This make it

Re: [PATCH v2 0/2] gfs2: Stop using rhashtable_walk_peek

On Thu, Mar 29, 2018 at 06:52:34PM +0200, Andreas Gruenbacher wrote: > > Should rhashtable_walk_peek be kept around even if there are no more > users? I have my doubts. Absolutely. All netlink dumps using rhashtable_walk_next are buggy and need to switch over to rhashtable_walk_peek. As

Re: [PATCH v2 0/2] gfs2: Stop using rhashtable_walk_peek

On Thu, Mar 29, 2018 at 06:52:34PM +0200, Andreas Gruenbacher wrote: > > Should rhashtable_walk_peek be kept around even if there are no more > users? I have my doubts. Absolutely. All netlink dumps using rhashtable_walk_next are buggy and need to switch over to rhashtable_walk_peek. As

Re: [PATCH 4/6] fpga: region: change fpga_region_register to have one param

On Thu, Mar 29, 2018 at 08:36:56AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_region_register to only take one parameter: > > int fpga_region_register(struct fpga_region *region) > > The parent dev is added to struct fpga_region. > > This make it similar to

Re: [PATCH 3/6] fpga: bridge: don't use drvdata in common fpga code

On Thu, Mar 29, 2018 at 08:36:55AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_bridge_register to not set drvdata. > > Change the register/unregister functions parameters to take the > bridge struct: > * int fpga_bridge_register(struct fpga_bridge *bridge);

Re: [PATCH 3/6] fpga: bridge: don't use drvdata in common fpga code

On Thu, Mar 29, 2018 at 08:36:55AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_bridge_register to not set drvdata. > > Change the register/unregister functions parameters to take the > bridge struct: > * int fpga_bridge_register(struct fpga_bridge *bridge); > * void

Re: [PATCH 2/6] fpga: manager: don't use drvdata in common fpga code

On Thu, Mar 29, 2018 at 08:36:54AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_mgr_register to not set or use drvdata. > > Change the register/unregister function parameters to take the mgr > struct: > * int fpga_mgr_register(struct fpga_manager *mgr); > *

Re: [PATCH 2/6] fpga: manager: don't use drvdata in common fpga code

On Thu, Mar 29, 2018 at 08:36:54AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_mgr_register to not set or use drvdata. > > Change the register/unregister function parameters to take the mgr > struct: > * int fpga_mgr_register(struct fpga_manager *mgr); > * void

Re: [PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

On 29/03/18 10:52 AM, James Smart wrote: > overall - I'm a little concerned about the replacement. > > I know the code depends on the null/zero checks in > nvmet_fc_free_tgt_pgs() as there are paths that can call them twice.  > Your replacement in that routine is fine, but you've fully

Re: [PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

On 29/03/18 10:52 AM, James Smart wrote: > overall - I'm a little concerned about the replacement. > > I know the code depends on the null/zero checks in > nvmet_fc_free_tgt_pgs() as there are paths that can call them twice.  > Your replacement in that routine is fine, but you've fully

Re: [PATCH 1/6] fpga: region: don't use drvdata in common fpga code

On Thu, Mar 29, 2018 at 08:36:53AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Part of patchset that changes the following fpga_*_register > functions to not set drvdata: > * fpga_region_register. > * fpga_mgr_register > * fpga_bridge_register That's not what this

Re: [PATCH 1/6] fpga: region: don't use drvdata in common fpga code

On Thu, Mar 29, 2018 at 08:36:53AM -0700, Moritz Fischer wrote: > From: Alan Tull > > Part of patchset that changes the following fpga_*_register > functions to not set drvdata: > * fpga_region_register. > * fpga_mgr_register > * fpga_bridge_register That's not what this specific patch does.

[PATCH] ath10k: fix spelling mistake: "tiggers" -> "triggers"

From: Colin Ian King Trivial fix to spelling mistake in message text Signed-off-by: Colin Ian King --- drivers/net/wireless/ath/ath10k/wmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ath10k: fix spelling mistake: "tiggers" -> "triggers"

From: Colin Ian King Trivial fix to spelling mistake in message text Signed-off-by: Colin Ian King --- drivers/net/wireless/ath/ath10k/wmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c index

Re: [PATCH 0/6] FPGA Manager Patches for 4.17

On Thu, Mar 29, 2018 at 08:36:52AM -0700, Moritz Fischer wrote: > Hi Greg, > > can you please take the following patches for 4.17. > > Alan's changes are mostly refactoring in preparation for non-dt based > FPGA regions. > > Anatolij's changes fix a small issue with altera-ps-spi FPGAs, > where

Re: [PATCH 0/6] FPGA Manager Patches for 4.17

On Thu, Mar 29, 2018 at 08:36:52AM -0700, Moritz Fischer wrote: > Hi Greg, > > can you please take the following patches for 4.17. > > Alan's changes are mostly refactoring in preparation for non-dt based > FPGA regions. > > Anatolij's changes fix a small issue with altera-ps-spi FPGAs, > where

Re: [PATCH 10/10] softirq: Remove __ARCH_SET_SOFTIRQ_PENDING

On Thu, Mar 29, 2018 at 04:53:43PM +0200, Martin Schwidefsky wrote: > On Thu, 29 Mar 2018 16:07:49 +0200 > Frederic Weisbecker wrote: > > > On Thu, Mar 29, 2018 at 04:01:11PM +0200, Peter Zijlstra wrote: > > > On Thu, Mar 29, 2018 at 03:47:46PM +0200, Frederic Weisbecker

Re: [PATCH 10/10] softirq: Remove __ARCH_SET_SOFTIRQ_PENDING

On Thu, Mar 29, 2018 at 04:53:43PM +0200, Martin Schwidefsky wrote: > On Thu, 29 Mar 2018 16:07:49 +0200 > Frederic Weisbecker wrote: > > > On Thu, Mar 29, 2018 at 04:01:11PM +0200, Peter Zijlstra wrote: > > > On Thu, Mar 29, 2018 at 03:47:46PM +0200, Frederic Weisbecker wrote: > > > > On Thu,

Re: general protection fault in try_to_wake_up

On Thu, Mar 29, 2018 at 6:32 PM, Steven Rostedt wrote: > > Not sure why we are being Cc'd on this crash. > > On Thu, 29 Mar 2018 09:01:02 -0700 > syzbot wrote: > >> Hello, >> >> syzbot hit the following crash on upstream

Re: general protection fault in try_to_wake_up

On Thu, Mar 29, 2018 at 6:32 PM, Steven Rostedt wrote: > > Not sure why we are being Cc'd on this crash. > > On Thu, 29 Mar 2018 09:01:02 -0700 > syzbot wrote: > >> Hello, >> >> syzbot hit the following crash on upstream commit >> bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12

[PATCH] dmaengine: rcar-dmac: Fix too early/late system suspend/resume callbacks

If serial console wake-up is enabled ("echo enabled > /sys/.../ttySC0/power/wakeup"), and any serial input is received while the system is suspended, serial port input no longer works after system resume. Note that: 1) The system can still be woken up using the serial console, 2) Serial port

[PATCH] dmaengine: rcar-dmac: Fix too early/late system suspend/resume callbacks

If serial console wake-up is enabled ("echo enabled > /sys/.../ttySC0/power/wakeup"), and any serial input is received while the system is suspended, serial port input no longer works after system resume. Note that: 1) The system can still be woken up using the serial console, 2) Serial port

[PATCH] ath6kl: fix spelling mistake: "chache" -> "cache"

From: Colin Ian King Trivial fix to spelling mistake in message text Signed-off-by: Colin Ian King --- drivers/net/wireless/ath/ath6kl/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ath6kl: fix spelling mistake: "chache" -> "cache"

From: Colin Ian King Trivial fix to spelling mistake in message text Signed-off-by: Colin Ian King --- drivers/net/wireless/ath/ath6kl/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath6kl/debug.c b/drivers/net/wireless/ath/ath6kl/debug.c

Re: [PATCH v2 0/2] gfs2: Stop using rhashtable_walk_peek

On 29 March 2018 at 17:41, Herbert Xu wrote: > On Thu, Mar 29, 2018 at 03:15:54PM +0200, Andreas Gruenbacher wrote: >> >> For all I know, Neil's latest plan is to get rhashtable_walk_peek >> replaced and removed because it is unfixable. This patch removes the >> one

Re: [PATCH v2 0/2] gfs2: Stop using rhashtable_walk_peek

On 29 March 2018 at 17:41, Herbert Xu wrote: > On Thu, Mar 29, 2018 at 03:15:54PM +0200, Andreas Gruenbacher wrote: >> >> For all I know, Neil's latest plan is to get rhashtable_walk_peek >> replaced and removed because it is unfixable. This patch removes the >> one and only user. > > His latest

Re: [PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

overall - I'm a little concerned about the replacement. I know the code depends on the null/zero checks in nvmet_fc_free_tgt_pgs() as there are paths that can call them twice.  Your replacement in that routine is fine, but you've fully removed any initialization to zero or setting to zero on

Re: [PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

overall - I'm a little concerned about the replacement. I know the code depends on the null/zero checks in nvmet_fc_free_tgt_pgs() as there are paths that can call them twice.  Your replacement in that routine is fine, but you've fully removed any initialization to zero or setting to zero on

RE: [PATCH v5 07/12] PCI: cadence: Set PCI_BASE_ADDRESS_MEM_TYPE_64 if a 64-bit BAR was set-up

On Wed, Mar 28, 2018 at 20:37, Bjorn Helgaas wrote: > On Wed, Mar 28, 2018 at 01:24:10PM +, Alan Douglas wrote: > > > On 28/03/2018 12:51, Niklas Cassel wrote: > > > cdns_pcie_ep_set_bar() does some round-up of the BAR size, which > > > means that a 64-bit BAR can be set-up, even when the flag

RE: [PATCH v5 07/12] PCI: cadence: Set PCI_BASE_ADDRESS_MEM_TYPE_64 if a 64-bit BAR was set-up

On Wed, Mar 28, 2018 at 20:37, Bjorn Helgaas wrote: > On Wed, Mar 28, 2018 at 01:24:10PM +, Alan Douglas wrote: > > > On 28/03/2018 12:51, Niklas Cassel wrote: > > > cdns_pcie_ep_set_bar() does some round-up of the BAR size, which > > > means that a 64-bit BAR can be set-up, even when the flag

Re: [PATCH 8/8] fs/aio: Use rcu_work instead of explicit rcu and work item

On 03/27, Tejun Heo wrote: > > On Tue, Mar 27, 2018 at 04:28:48PM +0200, Oleg Nesterov wrote: > > > flush_*work() guarantees to wait for the completion of the latest > > > instance of the work item which was visible to the caller. We can't > > > guarantee that w/o rcu_barrier(). > > > > And this

Re: [PATCH 8/8] fs/aio: Use rcu_work instead of explicit rcu and work item

On 03/27, Tejun Heo wrote: > > On Tue, Mar 27, 2018 at 04:28:48PM +0200, Oleg Nesterov wrote: > > > flush_*work() guarantees to wait for the completion of the latest > > > instance of the work item which was visible to the caller. We can't > > > guarantee that w/o rcu_barrier(). > > > > And this

Re: Reduce init time of `lp_init()` and `ppdev_init()`

On Thu, Mar 29, 2018 at 05:57:20PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > I am trying to reduce the start-up time of the Linux kernel on an old Lenovo > X60. Looking through the time stamps of Linux 4.16-rc7+, the modules `lp` > and `ppdev` both take more than ten milliseconds to

Re: Reduce init time of `lp_init()` and `ppdev_init()`

On Thu, Mar 29, 2018 at 05:57:20PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > I am trying to reduce the start-up time of the Linux kernel on an old Lenovo > X60. Looking through the time stamps of Linux 4.16-rc7+, the modules `lp` > and `ppdev` both take more than ten milliseconds to

Re: [PATCH AUTOSEL for 4.4 016/115] drm: Defer disabling the vblank IRQ until the next interrupt (for instant-off)

On Thu, Mar 29, 2018 at 05:32:13PM +0100, Ben Hutchings wrote: > On Sat, 2018-03-03 at 22:30 +, Sasha Levin wrote: > > From: Chris Wilson > > > > [ Upstream commit 608b20506941969ea30d8c08dc9ae02bb87dbf7d ] > > I think we need this one too: > > commit

Re: [PATCH AUTOSEL for 4.4 016/115] drm: Defer disabling the vblank IRQ until the next interrupt (for instant-off)

On Thu, Mar 29, 2018 at 05:32:13PM +0100, Ben Hutchings wrote: > On Sat, 2018-03-03 at 22:30 +, Sasha Levin wrote: > > From: Chris Wilson > > > > [ Upstream commit 608b20506941969ea30d8c08dc9ae02bb87dbf7d ] > > I think we need this one too: > > commit

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

* Pavel Machek [180329 16:38]: > Hi! > > > > > > And I do hear a voice talking over the speakerphone :) Sorry have not > > > > > tested the > > > > > mic yet.. > > > > > > And calling a person I can hear the other end but the mic is > > > not working. So maybe I need to tweak the

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

* Pavel Machek [180329 16:38]: > Hi! > > > > > > And I do hear a voice talking over the speakerphone :) Sorry have not > > > > > tested the > > > > > mic yet.. > > > > > > And calling a person I can hear the other end but the mic is > > > not working. So maybe I need to tweak the alsamixer

Re: [GIT PULL 00/10] stm class/intel_th: Updates for v4.17

c57b1b2: > > Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git > tags/stm-intel_th-for-greg-20180329 All pulled in, thanks. greg k-h

Re: [GIT PULL 00/10] stm class/intel_th: Updates for v4.17

c57b1b2: > > Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git > tags/stm-intel_th-for-greg-20180329 All pulled in, thanks. greg k-h

Re: [PATCH 2/3] virt: vbox: Use __get_free_pages instead of kmalloc for DMA32 memory

On Thu, Mar 29, 2018 at 03:42:59PM +0200, Hans de Goede wrote: > Hi, > > On 29-03-18 13:58, Greg Kroah-Hartman wrote: > > On Thu, Mar 29, 2018 at 01:21:15PM +0200, Hans de Goede wrote: > > > It is not possible to get DMA32 zone memory through kmalloc, > > > > Why can't we just fix that issue

Re: [PATCH 2/3] virt: vbox: Use __get_free_pages instead of kmalloc for DMA32 memory

On Thu, Mar 29, 2018 at 03:42:59PM +0200, Hans de Goede wrote: > Hi, > > On 29-03-18 13:58, Greg Kroah-Hartman wrote: > > On Thu, Mar 29, 2018 at 01:21:15PM +0200, Hans de Goede wrote: > > > It is not possible to get DMA32 zone memory through kmalloc, > > > > Why can't we just fix that issue

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 29/03/18 10:14 AM, Bart Van Assche wrote: > On Thu, 2018-03-29 at 10:07 -0600, Logan Gunthorpe wrote: >> +ret = fc_dma_map_sg(fod->tgtport->dev, sg, nent, >> +((fod->io_dir == NVMET_FCP_WRITE) ? >> +DMA_FROM_DEVICE : DMA_TO_DEVICE));

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 29/03/18 10:14 AM, Bart Van Assche wrote: > On Thu, 2018-03-29 at 10:07 -0600, Logan Gunthorpe wrote: >> +ret = fc_dma_map_sg(fod->tgtport->dev, sg, nent, >> +((fod->io_dir == NVMET_FCP_WRITE) ? >> +DMA_FROM_DEVICE : DMA_TO_DEVICE));

[PATCH v7] fs: Add VirtualBox guest shared folder (vboxsf) support

VirtualBox hosts can share folders with guests, this commit adds a VFS driver implementing the Linux-guest side of this, allowing folders exported by the host to be mounted under Linux. This driver depends on the guest <-> host IPC functions exported by the vboxguest driver. Signed-off-by: Hans

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On Thu, Mar 29, 2018 at 09:37:15AM -0500, Andy Gross wrote: > > Feel free to send your own contributions where you are adding the things that > are important to you. You can count on it. I am really happy that ipq4019 at least boots mainline. BTW is there any hope of getting a working mainline

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On Thu, Mar 29, 2018 at 09:37:15AM -0500, Andy Gross wrote: > > Feel free to send your own contributions where you are adding the things that > are important to you. You can count on it. I am really happy that ipq4019 at least boots mainline. BTW is there any hope of getting a working mainline

[PATCH v7] fs: Add VirtualBox guest shared folder (vboxsf) support

VirtualBox hosts can share folders with guests, this commit adds a VFS driver implementing the Linux-guest side of this, allowing folders exported by the host to be mounted under Linux. This driver depends on the guest <-> host IPC functions exported by the vboxguest driver. Signed-off-by: Hans

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi! > > > > And I do hear a voice talking over the speakerphone :) Sorry have not > > > > tested the > > > > mic yet.. > > > > And calling a person I can hear the other end but the mic is > > not working. So maybe I need to tweak the alsamixer settings > > too for mic? > > Your override kills

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi! > > > > And I do hear a voice talking over the speakerphone :) Sorry have not > > > > tested the > > > > mic yet.. > > > > And calling a person I can hear the other end but the mic is > > not working. So maybe I need to tweak the alsamixer settings > > too for mic? > > Your override kills

Re: [PATCH v7 08/14] mm, dax: enable filesystems to trigger dev_pagemap ->page_free callbacks

On Wed 21-03-18 15:57:53, Dan Williams wrote: > In order to resolve collisions between filesystem operations and DMA to > DAX mapped pages we need a callback when DMA completes. With a callback > we can hold off filesystem operations while DMA is in-flight and then > resume those operations when

Re: [PATCH v7 08/14] mm, dax: enable filesystems to trigger dev_pagemap ->page_free callbacks

On Wed 21-03-18 15:57:53, Dan Williams wrote: > In order to resolve collisions between filesystem operations and DMA to > DAX mapped pages we need a callback when DMA completes. With a callback > we can hold off filesystem operations while DMA is in-flight and then > resume those operations when

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

* Pavel Machek [180329 16:09]: > > Then using the n_gsm ts 27.010 uart mux, I dial: > > > > ./ngsm-rw 1 "AT+CFUN=1" # connect to network > > U0001+CFUN:OK > > ./ngsm-rw 2 "AT+CMUT=0" # unmute speaker over ch2, do this over > > qmi? > > U0001+CMUT:OK > >

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

* Pavel Machek [180329 16:09]: > > Then using the n_gsm ts 27.010 uart mux, I dial: > > > > ./ngsm-rw 1 "AT+CFUN=1" # connect to network > > U0001+CFUN:OK > > ./ngsm-rw 2 "AT+CMUT=0" # unmute speaker over ch2, do this over > > qmi? > > U0001+CMUT:OK > > ./ngsm-rw 1

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 3/29/2018 9:30 AM, Logan Gunthorpe wrote: Can you elaborate? The 'data_sg_cnt' member was in 'struct nvmet_fc_fcp_iod' which is declared in fc.c so it doesn't seem sane for lower driver to access it... In fact the next patch in the series removes it completely. Logan actually, I do think

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 3/29/2018 9:30 AM, Logan Gunthorpe wrote: Can you elaborate? The 'data_sg_cnt' member was in 'struct nvmet_fc_fcp_iod' which is declared in fc.c so it doesn't seem sane for lower driver to access it... In fact the next patch in the series removes it completely. Logan actually, I do think

Re: [net-next PATCH v2 05/10] net: netcp: ethss: use rgmii link status for 2u cpsw hardware

On 03/27/2018 01:29 PM, Andrew Lunn wrote: > On Tue, Mar 27, 2018 at 12:31:44PM -0400, Murali Karicheri wrote: >> Introduce rgmii link status to handle link state events for 2u >> cpsw hardware on K2G. >> >> Signed-off-by: Murali Karicheri >> --- >>

Re: [net-next PATCH v2 05/10] net: netcp: ethss: use rgmii link status for 2u cpsw hardware

On 03/27/2018 01:29 PM, Andrew Lunn wrote: > On Tue, Mar 27, 2018 at 12:31:44PM -0400, Murali Karicheri wrote: >> Introduce rgmii link status to handle link state events for 2u >> cpsw hardware on K2G. >> >> Signed-off-by: Murali Karicheri >> --- >> drivers/net/ethernet/ti/netcp_ethss.c | 27

Re: general protection fault in try_to_wake_up

Not sure why we are being Cc'd on this crash. On Thu, 29 Mar 2018 09:01:02 -0700 syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +) >

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On Thu, Mar 29, 2018 at 09:37:15AM -0500, Andy Gross wrote: > > If you aren't actually testing/validating this specific board, how can you > make > a statement like this? Unless you have tested these specifically on this > board, > I'd appreciate not getting false information about what is or

Re: general protection fault in try_to_wake_up

Not sure why we are being Cc'd on this crash. On Thu, 29 Mar 2018 09:01:02 -0700 syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +) > Merge tag 'pinctrl-v4.16-3' of >

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On Thu, Mar 29, 2018 at 09:37:15AM -0500, Andy Gross wrote: > > If you aren't actually testing/validating this specific board, how can you > make > a statement like this? Unless you have tested these specifically on this > board, > I'd appreciate not getting false information about what is or

Re: [PATCH AUTOSEL for 4.4 016/115] drm: Defer disabling the vblank IRQ until the next interrupt (for instant-off)

On Sat, 2018-03-03 at 22:30 +, Sasha Levin wrote: > From: Chris Wilson > > [ Upstream commit 608b20506941969ea30d8c08dc9ae02bb87dbf7d ] I think we need this one too: commit 75cff0837c14eaf632efabb8d7ab9eec6394d20d Author: Chris Wilson

Re: [PATCH AUTOSEL for 4.4 016/115] drm: Defer disabling the vblank IRQ until the next interrupt (for instant-off)

On Sat, 2018-03-03 at 22:30 +, Sasha Levin wrote: > From: Chris Wilson > > [ Upstream commit 608b20506941969ea30d8c08dc9ae02bb87dbf7d ] I think we need this one too: commit 75cff0837c14eaf632efabb8d7ab9eec6394d20d Author: Chris Wilson Date:   Fri Mar 24 17:30:58 2017 + drm: Make

RE: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

> Hmm, if we shrink llc-size by splitting it, do we also need to create a > unique "id" for each slice? RDT uses the cache id ... but it doesn't play well with cluster on die mode ... so our recommendation is to not use RDT if COD mode is enabled. If the result of these changes happens to be

RE: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

> Hmm, if we shrink llc-size by splitting it, do we also need to create a > unique "id" for each slice? RDT uses the cache id ... but it doesn't play well with cluster on die mode ... so our recommendation is to not use RDT if COD mode is enabled. If the result of these changes happens to be

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 29/03/18 10:24 AM, James Smart wrote: > Signed-off-by: James Smart  Thanks James. > As for "not used anywhere", be careful as the structure being prepped is > passed from the nvme-fc transport to an underlying lldd. So the > references would likely be in the

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 29/03/18 10:24 AM, James Smart wrote: > Signed-off-by: James Smart  Thanks James. > As for "not used anywhere", be careful as the structure being prepped is > passed from the nvme-fc transport to an underlying lldd. So the > references would likely be in the lldd. Can you elaborate? The

Re: [PATCH v5 15/16] sh: Switch to generic free_initrd_mem.

On Thu, Mar 29, 2018 at 07:32:06AM -0400, Shea Levy wrote: > The generic implementation is functionally identical. > > Signed-off-by: Shea Levy > --- > arch/sh/mm/init.c | 7 --- > 1 file changed, 7 deletions(-) > > diff --git a/arch/sh/mm/init.c b/arch/sh/mm/init.c >

Re: [PATCH v5 15/16] sh: Switch to generic free_initrd_mem.

On Thu, Mar 29, 2018 at 07:32:06AM -0400, Shea Levy wrote: > The generic implementation is functionally identical. > > Signed-off-by: Shea Levy > --- > arch/sh/mm/init.c | 7 --- > 1 file changed, 7 deletions(-) > > diff --git a/arch/sh/mm/init.c b/arch/sh/mm/init.c > index

Re: [PATCH 2/8] PCI: Add pci_find_common_upstream_dev()

On 29/03/18 10:10 AM, Christian König wrote: > Why not? I mean the dma_map_resource() function is for P2P while other > dma_map_* functions are only for system memory. Oh, hmm, I wasn't aware dma_map_resource was exclusively for mapping P2P. Though it's a bit odd seeing we've been working

Re: [PATCH 2/8] PCI: Add pci_find_common_upstream_dev()

On 29/03/18 10:10 AM, Christian König wrote: > Why not? I mean the dma_map_resource() function is for P2P while other > dma_map_* functions are only for system memory. Oh, hmm, I wasn't aware dma_map_resource was exclusively for mapping P2P. Though it's a bit odd seeing we've been working

Re: [net-next PATCH v2 03/10] net: netcp: ethss: make call to gbe_sgmii_config() conditional

On 03/27/2018 01:18 PM, Andrew Lunn wrote: > On Tue, Mar 27, 2018 at 12:31:42PM -0400, Murali Karicheri wrote: >> As a preparatory patch to add support for 2u cpsw hardware found on >> K2G SoC, make call to gbe_sgmii_config() conditional. This is required >> since 2u uses RGMII interface instead

Re: [net-next PATCH v2 03/10] net: netcp: ethss: make call to gbe_sgmii_config() conditional

On 03/27/2018 01:18 PM, Andrew Lunn wrote: > On Tue, Mar 27, 2018 at 12:31:42PM -0400, Murali Karicheri wrote: >> As a preparatory patch to add support for 2u cpsw hardware found on >> K2G SoC, make call to gbe_sgmii_config() conditional. This is required >> since 2u uses RGMII interface instead

Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

On 03/29/2018 09:09 AM, Peter Zijlstra wrote: > On Thu, Mar 29, 2018 at 07:34:58AM -0700, Dave Hansen wrote: >> What should we say, though? >> >> /* >>* false means 'c' does not share the LLC of 'o'. >>* Note: this decision gets reflected all the way >>

Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

On 03/29/2018 09:09 AM, Peter Zijlstra wrote: > On Thu, Mar 29, 2018 at 07:34:58AM -0700, Dave Hansen wrote: >> What should we say, though? >> >> /* >>* false means 'c' does not share the LLC of 'o'. >>* Note: this decision gets reflected all the way >>

Re: [RFC PATCH for 4.17 02/21] rseq: Introduce restartable sequences system call (v12)

On Thu, 29 Mar 2018 11:39:00 -0400 (EDT) Mathieu Desnoyers wrote: > Enforcing SIGSEGV on syscall entry when nested in a rseq critical section > will not be free both in terms of syscall overhead, and in terms of code > maintenance: we'd need to add those checks

Re: [RFC PATCH for 4.17 02/21] rseq: Introduce restartable sequences system call (v12)

On Thu, 29 Mar 2018 11:39:00 -0400 (EDT) Mathieu Desnoyers wrote: > Enforcing SIGSEGV on syscall entry when nested in a rseq critical section > will not be free both in terms of syscall overhead, and in terms of code > maintenance: we'd need to add those checks into entry.S for each architecture

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