RE: [PATCH v3 0/7] Add RSS to DPAA 1.x Ethernet driver

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Subject: Re: [PATCH v3 0/7] Add RSS to DPAA 1.x Ethernet driver > > From: David Miller > Date: Thu, 24 Aug 2017 09:42:20 -0700 (PDT) > > > From: Madalin Bucur > > Date:

RE: [PATCH v3 0/7] Add RSS to DPAA 1.x Ethernet driver

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Subject: Re: [PATCH v3 0/7] Add RSS to DPAA 1.x Ethernet driver > > From: David Miller > Date: Thu, 24 Aug 2017 09:42:20 -0700 (PDT) > > > From: Madalin Bucur > > Date: Thu, 24 Aug 2017 10:28:21 +0300 > > > >>

[PATCH] trace-cmd report: Fix hash.key in option -w

From: "Ziqian SUN (Zamir)" In add_wakeup function the hash list is created with hash.key = value. This makes add_sched function will never find a match with the key which results in trace-cmd report will never show the average latency with the following command: trace-cmd report

[PATCH] trace-cmd report: Fix hash.key in option -w

From: "Ziqian SUN (Zamir)" In add_wakeup function the hash list is created with hash.key = value. This makes add_sched function will never find a match with the key which results in trace-cmd report will never show the average latency with the following command: trace-cmd report -w -F

Re: [PATCH 05/14] kexec_file: factor out crashdump elf header function from x86

On 08/24/17 at 05:18pm, AKASHI Takahiro wrote: > prepare_elf_headers() can also be useful for other architectures, > including arm64. So let it factored out. > > Signed-off-by: AKASHI Takahiro > Cc: Dave Young > Cc: Vivek Goyal

Re: [PATCH 05/14] kexec_file: factor out crashdump elf header function from x86

On 08/24/17 at 05:18pm, AKASHI Takahiro wrote: > prepare_elf_headers() can also be useful for other architectures, > including arm64. So let it factored out. > > Signed-off-by: AKASHI Takahiro > Cc: Dave Young > Cc: Vivek Goyal > Cc: Baoquan He > --- > arch/x86/kernel/crash.c | 324

[PATCH] net: sxgbe: check memory allocation failure

Check memory allocation failure and return -ENOMEM in such a case, as already done few lines below for another memory allocation. Signed-off-by: Christophe JAILLET --- drivers/net/ethernet/samsung/sxgbe/sxgbe_platform.c | 2 ++ 1 file changed, 2 insertions(+)

[PATCH] net: sxgbe: check memory allocation failure

Check memory allocation failure and return -ENOMEM in such a case, as already done few lines below for another memory allocation. Signed-off-by: Christophe JAILLET --- drivers/net/ethernet/samsung/sxgbe/sxgbe_platform.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH] zram: add zstd to the supported algorithms list

On Fri, Aug 25, 2017 at 02:06:44PM +0900, Sergey Senozhatsky wrote: < snip > > > Off-topic: > > > > In all ways, zstd beats deflate. Nick, Right? > > > > With zstd, I doubt we should show "deflate" to user. Many options just > > make user confused. > > The inflate have been there for

Re: [PATCH] zram: add zstd to the supported algorithms list

On Fri, Aug 25, 2017 at 02:06:44PM +0900, Sergey Senozhatsky wrote: < snip > > > Off-topic: > > > > In all ways, zstd beats deflate. Nick, Right? > > > > With zstd, I doubt we should show "deflate" to user. Many options just > > make user confused. > > The inflate have been there for

Re: [PATCH 1/2] xfs: cache dax_device lookup result

On Thu, Aug 24, 2017 at 05:35:48PM -0700, Dan Williams wrote: > The ->iomap_begin() operation is a hot path, so cache the > fs_dax_get_by_host() result to avoid the incurring the hash lookup > overhead. Just out of curiosity (and sorry if this has already been discussed to death and I'm merely

Re: [PATCH 1/2] xfs: cache dax_device lookup result

On Thu, Aug 24, 2017 at 05:35:48PM -0700, Dan Williams wrote: > The ->iomap_begin() operation is a hot path, so cache the > fs_dax_get_by_host() result to avoid the incurring the hash lookup > overhead. Just out of curiosity (and sorry if this has already been discussed to death and I'm merely

[PATCH manpages] stat.2: correct AT_NO_AUTOMOUNT text and general revisions.

Expand on the relationship between fstatat() and the other three functions, and improve the description of AT_NO_AUTOMOUNT. Specifically, both stat() and lstat() act the same way with respect to automounts, and that behavior matches fstatat with the AT_NO_AUTOMOUNT flag. The text in the NOTES

[PATCH manpages] stat.2: correct AT_NO_AUTOMOUNT text and general revisions.

Expand on the relationship between fstatat() and the other three functions, and improve the description of AT_NO_AUTOMOUNT. Specifically, both stat() and lstat() act the same way with respect to automounts, and that behavior matches fstatat with the AT_NO_AUTOMOUNT flag. The text in the NOTES

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 14:06), Sergey Senozhatsky wrote: > > Off-topic: > > > > In all ways, zstd beats deflate. Nick, Right? > > > > With zstd, I doubt we should show "deflate" to user. Many options just > > make user confused. > > The inflate have been there for representing high comp ratio but slower >

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 14:06), Sergey Senozhatsky wrote: > > Off-topic: > > > > In all ways, zstd beats deflate. Nick, Right? > > > > With zstd, I doubt we should show "deflate" to user. Many options just > > make user confused. > > The inflate have been there for representing high comp ratio but slower >

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 02:46), Nick Terrell wrote: > On 8/24/17, 7:21 PM, "Sergey Senozhatsky" > wrote: > > not really familiar either... I was thinking about having "zstd" and > > "zstd_dict" crypto_alg structs - one would be !dict, the other one would > > allocate dict

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 02:46), Nick Terrell wrote: > On 8/24/17, 7:21 PM, "Sergey Senozhatsky" > wrote: > > not really familiar either... I was thinking about having "zstd" and > > "zstd_dict" crypto_alg structs - one would be !dict, the other one would > > allocate dict and pass it to compress/decompress

[PATCH] usb: chipidea: usb2: check memory allocation failure

Check memory allocation failure and return -ENOMEM in such a case, as already done few lines below for another memory allocation. Signed-off-by: Christophe JAILLET --- drivers/usb/chipidea/ci_hdrc_usb2.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH] usb: chipidea: usb2: check memory allocation failure

Check memory allocation failure and return -ENOMEM in such a case, as already done few lines below for another memory allocation. Signed-off-by: Christophe JAILLET --- drivers/usb/chipidea/ci_hdrc_usb2.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/usb/chipidea/ci_hdrc_usb2.c

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

On 2017/6/29 6:13, Thomas Gleixner wrote: > On Wed, 28 Jun 2017, zhong jiang wrote: >> On 2017/6/22 0:40, Ingo Molnar wrote: >>> * zhong jiang wrote: >>> when shift expoment is negative, left shift alway zero. therefore, we modify the logic to avoid the warining.

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

On 2017/6/29 6:13, Thomas Gleixner wrote: > On Wed, 28 Jun 2017, zhong jiang wrote: >> On 2017/6/22 0:40, Ingo Molnar wrote: >>> * zhong jiang wrote: >>> when shift expoment is negative, left shift alway zero. therefore, we modify the logic to avoid the warining.

Re: [PATCH] zram: add zstd to the supported algorithms list

Hi Nick, On Fri, Aug 25, 2017 at 01:35:35AM +, Nick Terrell wrote: > On 8/24/17, 5:49 PM, "Joonsoo Kim" wrote: > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > > > Add ZSTD

Re: [PATCH] zram: add zstd to the supported algorithms list

Hi Nick, On Fri, Aug 25, 2017 at 01:35:35AM +, Nick Terrell wrote: > On 8/24/17, 5:49 PM, "Joonsoo Kim" wrote: > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > > > Add ZSTD to the list of supported

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 13:50), Minchan Kim wrote: [..] > Thanks for the testing. > Could you resend the patch with this test result with my acked-by? ok. > Acked-by: Minchan Kim thanks. > Off-topic: > > In all ways, zstd beats deflate. Nick, Right? > > With zstd, I doubt we should

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 13:50), Minchan Kim wrote: [..] > Thanks for the testing. > Could you resend the patch with this test result with my acked-by? ok. > Acked-by: Minchan Kim thanks. > Off-topic: > > In all ways, zstd beats deflate. Nick, Right? > > With zstd, I doubt we should show "deflate" to

Re: [PATCH] strparser: initialize all callbacks

From: Eric Biggers Date: Thu, 24 Aug 2017 14:38:51 -0700 > From: Eric Biggers > > commit bbb03029a899 ("strparser: Generalize strparser") added more > function pointers to 'struct strp_callbacks'; however, kcm_attach() was > not updated to initialize

Re: [PATCH] strparser: initialize all callbacks

From: Eric Biggers Date: Thu, 24 Aug 2017 14:38:51 -0700 > From: Eric Biggers > > commit bbb03029a899 ("strparser: Generalize strparser") added more > function pointers to 'struct strp_callbacks'; however, kcm_attach() was > not updated to initialize them. This could cause the ->lock() and/or

Re: [PATCH net-next] hv_netvsc: Fix rndis_filter_close error during netvsc_remove

From: Haiyang Zhang Date: Thu, 24 Aug 2017 11:50:02 -0700 > From: Haiyang Zhang > > We now remove rndis filter before unregister_netdev(), which calls > device close. It involves closing rndis filter already removed. > > This patch

Re: [PATCH net-next] hv_netvsc: Fix rndis_filter_close error during netvsc_remove

From: Haiyang Zhang Date: Thu, 24 Aug 2017 11:50:02 -0700 > From: Haiyang Zhang > > We now remove rndis filter before unregister_netdev(), which calls > device close. It involves closing rndis filter already removed. > > This patch fixes this error. > > Signed-off-by: Haiyang Zhang

linux-next: manual merge of the kvm-arm tree with the arm64 tree

Hi all, Today's linux-next merge of the kvm-arm tree got a conflict in: arch/arm64/include/asm/esr.h between commit: 1f9b8936f36f ("arm64: Decode information from ESR upon mem faults") from the arm64 tree and commit: c5511c3c068c ("KVM: arm/arm64: Fix guest external abort matching")

linux-next: manual merge of the kvm-arm tree with the arm64 tree

Hi all, Today's linux-next merge of the kvm-arm tree got a conflict in: arch/arm64/include/asm/esr.h between commit: 1f9b8936f36f ("arm64: Decode information from ESR upon mem faults") from the arm64 tree and commit: c5511c3c068c ("KVM: arm/arm64: Fix guest external abort matching")

Re: [PATCH v6] mtd: sharpslpart: Add sharpslpart partition parser

On Thu, Aug 24, 2017 at 01:27:10PM +0200, Boris Brezillon wrote: > On Thu, 24 Aug 2017 12:30:02 +0200 > Andrea Adami wrote: > > > On Thu, Aug 24, 2017 at 12:04 PM, Boris Brezillon > > wrote: > > > On Thu, 24 Aug 2017 11:19:56 +0200 > >

Re: [PATCH v6] mtd: sharpslpart: Add sharpslpart partition parser

On Thu, Aug 24, 2017 at 01:27:10PM +0200, Boris Brezillon wrote: > On Thu, 24 Aug 2017 12:30:02 +0200 > Andrea Adami wrote: > > > On Thu, Aug 24, 2017 at 12:04 PM, Boris Brezillon > > wrote: > > > On Thu, 24 Aug 2017 11:19:56 +0200 > > > Andrea Adami wrote: ... > > >> >> + /* create

Re: [PATCH 2/2 v8] printk: Add monotonic, boottime, and realtime timestamps

On (08/24/17 09:42), Prarit Bhargava wrote: [..] > +config PRINTK_TIME_DEBUG > + bool "Allow runtime reselection of any timebase on printks" > + depends on PRINTK > + default N > + help > + Selecting this option causes time stamps of the printk() > + messages to be

Re: [PATCH 2/2 v8] printk: Add monotonic, boottime, and realtime timestamps

On (08/24/17 09:42), Prarit Bhargava wrote: [..] > +config PRINTK_TIME_DEBUG > + bool "Allow runtime reselection of any timebase on printks" > + depends on PRINTK > + default N > + help > + Selecting this option causes time stamps of the printk() > + messages to be

Re: [PATCH] zram: add zstd to the supported algorithms list

Hi Sergey, On Thu, Aug 24, 2017 at 11:04:40PM +0900, Sergey Senozhatsky wrote: > Hi, > > On (08/24/17 13:30), Minchan Kim wrote: > > Hello Sergey, > > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > > Add ZSTD to the list of supported compression algorithms. > > > >

Re: [PATCH] zram: add zstd to the supported algorithms list

Hi Sergey, On Thu, Aug 24, 2017 at 11:04:40PM +0900, Sergey Senozhatsky wrote: > Hi, > > On (08/24/17 13:30), Minchan Kim wrote: > > Hello Sergey, > > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > > Add ZSTD to the list of supported compression algorithms. > > > >

Re: [PATCH net-next 0/4] net: mvpp2: fix the mac address retrieval logic

From: Antoine Tenart Date: Thu, 24 Aug 2017 11:46:54 +0200 > The MAC address retrieval logic was broken and when using the PPv2 > driver on PPv2.2 engines I ended up using the same mac address on all > ports. This series of patches fixes this, and also tackle a

Re: [PATCH net-next 0/4] net: mvpp2: fix the mac address retrieval logic

From: Antoine Tenart Date: Thu, 24 Aug 2017 11:46:54 +0200 > The MAC address retrieval logic was broken and when using the PPv2 > driver on PPv2.2 engines I ended up using the same mac address on all > ports. This series of patches fixes this, and also tackle a possible bug > when defining the

linux-next: manual merge of the kvm tree with the tip tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/mmu.h between commit: d0ec49d4de90 ("kvm/x86/svm: Support Secure Memory Encryption within KVM") from the tip tree and commit: d1cd3ce90044 ("KVM: MMU: check guest CR3 reserved bits based on its physical

linux-next: manual merge of the kvm tree with the tip tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/mmu.h between commit: d0ec49d4de90 ("kvm/x86/svm: Support Secure Memory Encryption within KVM") from the tip tree and commit: d1cd3ce90044 ("KVM: MMU: check guest CR3 reserved bits based on its physical

Re: [PATCH 4/4] lockdep: Fix workqueue crossrelease annotation

On Thu, Aug 24, 2017 at 04:02:40PM +0200, Peter Zijlstra wrote: > > > + if (c == XHLOCK_PROC) { I found this now. Are you trying to invalidate it w/o checking force? No, we _should not_ do this. It's worse than work-around code. No reason to do this here. Please communicate with me more or

Re: [PATCH 4/4] lockdep: Fix workqueue crossrelease annotation

On Thu, Aug 24, 2017 at 04:02:40PM +0200, Peter Zijlstra wrote: > > > + if (c == XHLOCK_PROC) { I found this now. Are you trying to invalidate it w/o checking force? No, we _should not_ do this. It's worse than work-around code. No reason to do this here. Please communicate with me more or

Re: [PATCH net-next v2] net: mv643xx_eth: Be drop monitor friendly

On Thu, 2017-08-24 at 20:55 -0700, Florian Fainelli wrote: > txq_reclaim() does the normal transmit queue reclamation and > rxq_deinit() does the RX ring cleanup, none of these are packet drops, > so use dev_consume_skb() for both locations. > > Signed-off-by: Florian Fainelli

Re: [PATCH net-next v2] net: mv643xx_eth: Be drop monitor friendly

On Thu, 2017-08-24 at 20:55 -0700, Florian Fainelli wrote: > txq_reclaim() does the normal transmit queue reclamation and > rxq_deinit() does the RX ring cleanup, none of these are packet drops, > so use dev_consume_skb() for both locations. > > Signed-off-by: Florian Fainelli > --- >

linux-next: manual merge of the kvm tree with Linus' tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/include/asm/cpufeatures.h between commit: 5442c2699552 ("x86/cpufeature, kvm/svm: Rename (shorten) the new "virtualized VMSAVE/VMLOAD" CPUID flag") from Linus' tree and commit: d837312dfd5b ("KVM: SVM: Add

linux-next: manual merge of the kvm tree with Linus' tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/include/asm/cpufeatures.h between commit: 5442c2699552 ("x86/cpufeature, kvm/svm: Rename (shorten) the new "virtualized VMSAVE/VMLOAD" CPUID flag") from Linus' tree and commit: d837312dfd5b ("KVM: SVM: Add

Re: [PATCH net-next v2] e1000e: Be drop monitor friendly

From: Florian Fainelli Date: Thu, 24 Aug 2017 20:58:24 -0700 > e1000_put_txbuf() cleans up the successfully transmitted TX packets, > e1000e_tx_hwtstamp_work() also does the successfully completes the > timestamped TX packets, e1000_clean_rx_ring() cleans up the RX ring and

Re: [PATCH net-next v2] e1000e: Be drop monitor friendly

From: Florian Fainelli Date: Thu, 24 Aug 2017 20:58:24 -0700 > e1000_put_txbuf() cleans up the successfully transmitted TX packets, > e1000e_tx_hwtstamp_work() also does the successfully completes the > timestamped TX packets, e1000_clean_rx_ring() cleans up the RX ring and > e1000_remove()

Re: [PATCH net-next v2] net: mv643xx_eth: Be drop monitor friendly

From: Florian Fainelli Date: Thu, 24 Aug 2017 20:55:40 -0700 > txq_reclaim() does the normal transmit queue reclamation and > rxq_deinit() does the RX ring cleanup, none of these are packet drops, > so use dev_consume_skb() for both locations. > > Signed-off-by: Florian

Re: [PATCH net-next v2] net: mv643xx_eth: Be drop monitor friendly

From: Florian Fainelli Date: Thu, 24 Aug 2017 20:55:40 -0700 > txq_reclaim() does the normal transmit queue reclamation and > rxq_deinit() does the RX ring cleanup, none of these are packet drops, > so use dev_consume_skb() for both locations. > > Signed-off-by: Florian Fainelli Applied.

[git pull] drm fixes for 4.13-rc7

Hi Linus, Fixes for rc7, nothing too crazy, some core, i915, and sunxi fixes, Intel CI has been responsible for some of these fixes being required. Dave. The following changes since commit 14ccee78fc82f5512908f4424f541549a5705b89: Linux 4.13-rc6 (2017-08-20 14:13:52 -0700) are available in

[git pull] drm fixes for 4.13-rc7

Hi Linus, Fixes for rc7, nothing too crazy, some core, i915, and sunxi fixes, Intel CI has been responsible for some of these fixes being required. Dave. The following changes since commit 14ccee78fc82f5512908f4424f541549a5705b89: Linux 4.13-rc6 (2017-08-20 14:13:52 -0700) are available in

Re: [PATCH] xfs: Drop setting redundant PF_KSWAPD in kswapd context

On 08/25/2017 05:31 AM, Dave Chinner wrote: > On Thu, Aug 24, 2017 at 12:56:35PM +0200, Michal Hocko wrote: >> On Thu 24-08-17 16:12:47, Anshuman Khandual wrote: >>> xfs_btree_split() calls xfs_btree_split_worker() with args.kswapd set >>> if current->flags alrady has PF_KSWAPD. Hence we should

Re: [PATCH] xfs: Drop setting redundant PF_KSWAPD in kswapd context

On 08/25/2017 05:31 AM, Dave Chinner wrote: > On Thu, Aug 24, 2017 at 12:56:35PM +0200, Michal Hocko wrote: >> On Thu 24-08-17 16:12:47, Anshuman Khandual wrote: >>> xfs_btree_split() calls xfs_btree_split_worker() with args.kswapd set >>> if current->flags alrady has PF_KSWAPD. Hence we should

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On 08/24/2017 08:41 PM, Chen-Yu Tsai wrote: > On Fri, Aug 25, 2017 at 11:05 AM, Florian Fainelli > wrote: >> >> >> On 08/24/2017 07:54 PM, Chen-Yu Tsai wrote: >>> On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli >>> wrote: On 08/24/2017 01:21

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On 08/24/2017 08:41 PM, Chen-Yu Tsai wrote: > On Fri, Aug 25, 2017 at 11:05 AM, Florian Fainelli > wrote: >> >> >> On 08/24/2017 07:54 PM, Chen-Yu Tsai wrote: >>> On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli >>> wrote: On 08/24/2017 01:21 AM, Corentin Labbe wrote: > On Wed, Aug

[PATCH net-next v2] e1000e: Be drop monitor friendly

e1000_put_txbuf() cleans up the successfully transmitted TX packets, e1000e_tx_hwtstamp_work() also does the successfully completes the timestamped TX packets, e1000_clean_rx_ring() cleans up the RX ring and e1000_remove() cleans up the timestampted packets. None of these functions should be

[PATCH net-next v2] e1000e: Be drop monitor friendly

e1000_put_txbuf() cleans up the successfully transmitted TX packets, e1000e_tx_hwtstamp_work() also does the successfully completes the timestamped TX packets, e1000_clean_rx_ring() cleans up the RX ring and e1000_remove() cleans up the timestampted packets. None of these functions should be

[PATCH net-next v2] net: mv643xx_eth: Be drop monitor friendly

txq_reclaim() does the normal transmit queue reclamation and rxq_deinit() does the RX ring cleanup, none of these are packet drops, so use dev_consume_skb() for both locations. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/marvell/mv643xx_eth.c | 4 ++-- 1 file

[PATCH net-next v2] net: mv643xx_eth: Be drop monitor friendly

txq_reclaim() does the normal transmit queue reclamation and rxq_deinit() does the RX ring cleanup, none of these are packet drops, so use dev_consume_skb() for both locations. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/marvell/mv643xx_eth.c | 4 ++-- 1 file changed, 2

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On Fri, Aug 25, 2017 at 11:05 AM, Florian Fainelli wrote: > > > On 08/24/2017 07:54 PM, Chen-Yu Tsai wrote: >> On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli >> wrote: >>> On 08/24/2017 01:21 AM, Corentin Labbe wrote: On Wed, Aug 23, 2017 at

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On Fri, Aug 25, 2017 at 11:05 AM, Florian Fainelli wrote: > > > On 08/24/2017 07:54 PM, Chen-Yu Tsai wrote: >> On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli >> wrote: >>> On 08/24/2017 01:21 AM, Corentin Labbe wrote: On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote:

Re: [PATCH v7 04/12] powerpc/vas: Define helpers to access MMIO regions

Hi Suka, Comments inline. Sukadev Bhattiprolu writes: > diff --git a/arch/powerpc/platforms/powernv/vas-window.c > b/arch/powerpc/platforms/powernv/vas-window.c > index 6156fbe..a3a705a 100644 > --- a/arch/powerpc/platforms/powernv/vas-window.c > +++

Re: [PATCH v7 04/12] powerpc/vas: Define helpers to access MMIO regions

Hi Suka, Comments inline. Sukadev Bhattiprolu writes: > diff --git a/arch/powerpc/platforms/powernv/vas-window.c > b/arch/powerpc/platforms/powernv/vas-window.c > index 6156fbe..a3a705a 100644 > --- a/arch/powerpc/platforms/powernv/vas-window.c > +++

[v2] ARM: multi_v7_defconfig: make eSDHC driver built-in

Sometimes root file system is deployed on SD card. It's proper to build eSDHC driver into kernel. Signed-off-by: Yangbo Lu --- Changes for v2: - Added more reviewers (by get_maintainer.pl). --- arch/arm/configs/multi_v7_defconfig | 2 +- 1 file changed, 1

[v2] ARM: multi_v7_defconfig: make eSDHC driver built-in

Sometimes root file system is deployed on SD card. It's proper to build eSDHC driver into kernel. Signed-off-by: Yangbo Lu --- Changes for v2: - Added more reviewers (by get_maintainer.pl). --- arch/arm/configs/multi_v7_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

RE: [PATCH v2 net-next 1/1] hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

> From: David Miller [mailto:da...@davemloft.net] > Sent: Thursday, August 24, 2017 18:20 > > +#define VMBUS_PKT_TRAILER (sizeof(u64)) > > This is not the packet trailer, it's the size of the packet trailer. Thanks! I'll change it to VMBUS_PKT_TRAILER_SIZE. > > + /* Have we sent the

RE: [PATCH v2 net-next 1/1] hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

> From: David Miller [mailto:da...@davemloft.net] > Sent: Thursday, August 24, 2017 18:20 > > +#define VMBUS_PKT_TRAILER (sizeof(u64)) > > This is not the packet trailer, it's the size of the packet trailer. Thanks! I'll change it to VMBUS_PKT_TRAILER_SIZE. > > + /* Have we sent the

Re: [PATCH net-next] e1000e: Be drop monitor friendly

On 08/24/2017 06:36 PM, Florian Fainelli wrote: > e1000_put_txbuf() cleans up the successfully transmitted TX packets, > e1000e_tx_hwtstamp_work() also does the successfully completes the > timestamped TX packets, e1000_clean_rx_ring() cleans up the RX ring and > e1000_remove() cleans up the

Re: [PATCH net-next] e1000e: Be drop monitor friendly

On 08/24/2017 06:36 PM, Florian Fainelli wrote: > e1000_put_txbuf() cleans up the successfully transmitted TX packets, > e1000e_tx_hwtstamp_work() also does the successfully completes the > timestamped TX packets, e1000_clean_rx_ring() cleans up the RX ring and > e1000_remove() cleans up the

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On 08/24/2017 07:54 PM, Chen-Yu Tsai wrote: > On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli > wrote: >> On 08/24/2017 01:21 AM, Corentin Labbe wrote: >>> On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote: On 08/23/2017 12:49 AM, Maxime Ripard

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On 08/24/2017 07:54 PM, Chen-Yu Tsai wrote: > On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli > wrote: >> On 08/24/2017 01:21 AM, Corentin Labbe wrote: >>> On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote: On 08/23/2017 12:49 AM, Maxime Ripard wrote: > Hi Florian,

linux-next: manual merge of the sound-asoc tree with the sound-current tree

Hi all, Today's linux-next merge of the sound-asoc tree got a conflict in: sound/soc/codecs/rt5677.c between commit: 9ce76511b67b ("ASoC: rt5677: Reintroduce I2C device IDs") from the sound-current tree and commit: ddc9e69b9dc2 ("ASoC: rt5677: Hide platform data in the module sources")

linux-next: manual merge of the sound-asoc tree with the sound-current tree

Hi all, Today's linux-next merge of the sound-asoc tree got a conflict in: sound/soc/codecs/rt5677.c between commit: 9ce76511b67b ("ASoC: rt5677: Reintroduce I2C device IDs") from the sound-current tree and commit: ddc9e69b9dc2 ("ASoC: rt5677: Hide platform data in the module sources")

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli wrote: > On 08/24/2017 01:21 AM, Corentin Labbe wrote: >> On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote: >>> On 08/23/2017 12:49 AM, Maxime Ripard wrote: Hi Florian, On Tue, Aug 22, 2017 at

Re: [PATCH v3 3/4] net: stmmac: register parent MDIO node for sun8i-h3-emac

On Fri, Aug 25, 2017 at 3:59 AM, Florian Fainelli wrote: > On 08/24/2017 01:21 AM, Corentin Labbe wrote: >> On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote: >>> On 08/23/2017 12:49 AM, Maxime Ripard wrote: Hi Florian, On Tue, Aug 22, 2017 at 11:35:01AM -0700,

Re: [PATCH] zram: add zstd to the supported algorithms list

On 8/24/17, 7:21 PM, "Sergey Senozhatsky" wrote: > not really familiar either... I was thinking about having "zstd" and > "zstd_dict" crypto_alg structs - one would be !dict, the other one would > allocate dict and pass it to compress/decompress zstd callbacks.

Re: [PATCH] zram: add zstd to the supported algorithms list

On 8/24/17, 7:21 PM, "Sergey Senozhatsky" wrote: > not really familiar either... I was thinking about having "zstd" and > "zstd_dict" crypto_alg structs - one would be !dict, the other one would > allocate dict and pass it to compress/decompress zstd callbacks. "zstd" > vecrsion would invoke

Re: [PATCH 3/3] x86/efi: Use efi_switch_mm() rather than manually twiddling with cr3

On Tue, 2017-08-15 at 14:46 -0700, Andy Lutomirski wrote: > On Tue, Aug 15, 2017 at 12:18 PM, Sai Praneeth Prakhya > wrote: > > +/* > > + * Makes the calling kernel thread switch to/from efi_mm context > > + * Can be used from SetVirtualAddressMap() or during efi

Re: [PATCH 3/3] x86/efi: Use efi_switch_mm() rather than manually twiddling with cr3

On Tue, 2017-08-15 at 14:46 -0700, Andy Lutomirski wrote: > On Tue, Aug 15, 2017 at 12:18 PM, Sai Praneeth Prakhya > wrote: > > +/* > > + * Makes the calling kernel thread switch to/from efi_mm context > > + * Can be used from SetVirtualAddressMap() or during efi runtime calls > > + * (Note: This

Re: linux-next: Signed-off-by missing for commit in the nfsd tree

On Thu, Aug 24, 2017 at 10:21:41PM -0400, J. Bruce Fields wrote: > On Fri, Aug 25, 2017 at 08:48:21AM +1000, Stephen Rothwell wrote: > > Hi Bruce, > > > > Commit > > > > 1b7f1a85c0fa ("opdesc will be useful outside nfs4proc.c") > > > > is missing a Signed-off-by from its author and committer.

Re: linux-next: Signed-off-by missing for commit in the nfsd tree

On Thu, Aug 24, 2017 at 10:21:41PM -0400, J. Bruce Fields wrote: > On Fri, Aug 25, 2017 at 08:48:21AM +1000, Stephen Rothwell wrote: > > Hi Bruce, > > > > Commit > > > > 1b7f1a85c0fa ("opdesc will be useful outside nfs4proc.c") > > > > is missing a Signed-off-by from its author and committer.

Re: [PATCH v4 3/4] dt-bindings: PCI: rockchip: Add support for pcie wake irq

On 2017/8/25 10:11, Brian Norris wrote: On Thu, Aug 24, 2017 at 11:53:54AM -0500, Bjorn Helgaas wrote: On Tue, Aug 22, 2017 at 11:19:33AM +0800, Jeffy Chen wrote: Signed-off-by: Jeffy Chen diff --git a/Documentation/devicetree/bindings/pci/rockchip-pcie.txt

Re: [PATCH v4 3/4] dt-bindings: PCI: rockchip: Add support for pcie wake irq

On 2017/8/25 10:11, Brian Norris wrote: On Thu, Aug 24, 2017 at 11:53:54AM -0500, Bjorn Helgaas wrote: On Tue, Aug 22, 2017 at 11:19:33AM +0800, Jeffy Chen wrote: Signed-off-by: Jeffy Chen diff --git a/Documentation/devicetree/bindings/pci/rockchip-pcie.txt

Re: [PATCH] thermal: max77620: constify platform_device_id

On Sun, 2017-08-13 at 17:03 +0530, Arvind Yadav wrote: > platform_device_id are not supposed to change at runtime. All > functions > working with platform_device_id provided by > work with const platform_device_id. So mark the non-const structs as > const. > > Signed-off-by: Arvind Yadav

Re: [PATCH] thermal: max77620: constify platform_device_id

On Sun, 2017-08-13 at 17:03 +0530, Arvind Yadav wrote: > platform_device_id are not supposed to change at runtime. All > functions > working with platform_device_id provided by > work with const platform_device_id. So mark the non-const structs as > const. > > Signed-off-by: Arvind Yadav

Re: linux-next: Signed-off-by missing for commit in the nfsd tree

On Fri, Aug 25, 2017 at 08:48:21AM +1000, Stephen Rothwell wrote: > Hi Bruce, > > Commit > > 1b7f1a85c0fa ("opdesc will be useful outside nfs4proc.c") > > is missing a Signed-off-by from its author and committer. Fixed, thanks.--b.

Re: linux-next: Signed-off-by missing for commit in the nfsd tree

On Fri, Aug 25, 2017 at 08:48:21AM +1000, Stephen Rothwell wrote: > Hi Bruce, > > Commit > > 1b7f1a85c0fa ("opdesc will be useful outside nfs4proc.c") > > is missing a Signed-off-by from its author and committer. Fixed, thanks.--b.

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 02:09), Nick Terrell wrote: [..] > > > I think using dictionaries in zram could be very interesting. We could for > > > example, take a random sample of the RAM and use that as the dictionary > > > for compression. E.g. take 32 512B samples from RAM and build a 16 KB > > > dictionary

Re: [PATCH] zram: add zstd to the supported algorithms list

On (08/25/17 02:09), Nick Terrell wrote: [..] > > > I think using dictionaries in zram could be very interesting. We could for > > > example, take a random sample of the RAM and use that as the dictionary > > > for compression. E.g. take 32 512B samples from RAM and build a 16 KB > > > dictionary

Re: [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem

On Wed, 2017-08-16 at 18:33 +0300, Leonard Crestez wrote: > On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote: > > > > On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote: > > > > > > On 08/08/17 12:38, Leonard Crestez wrote: > > > > > > > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas

Re: [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem

On Wed, 2017-08-16 at 18:33 +0300, Leonard Crestez wrote: > On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote: > > > > On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote: > > > > > > On 08/08/17 12:38, Leonard Crestez wrote: > > > > > > > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas

Re: [PATCH V1] thermal: qcom-spmi-temp-alarm: add support for GEN2 PMIC peripherals

On Thu, 2017-08-17 at 13:12 +0530, kgu...@codeaurora.org wrote: > On 2017-08-16 17:53, kgu...@codeaurora.org wrote: > > > > On 2017-08-08 13:42, Zhang Rui wrote: > > > > > > On Thu, 2017-07-13 at 17:39 +0530, Kiran Gunda wrote: > > > > > > > > From: David Collins > > >

Re: [PATCH V1] thermal: qcom-spmi-temp-alarm: add support for GEN2 PMIC peripherals

On Thu, 2017-08-17 at 13:12 +0530, kgu...@codeaurora.org wrote: > On 2017-08-16 17:53, kgu...@codeaurora.org wrote: > > > > On 2017-08-08 13:42, Zhang Rui wrote: > > > > > > On Thu, 2017-07-13 at 17:39 +0530, Kiran Gunda wrote: > > > > > > > > From: David Collins > > > > > > > > Add support

Re: [PATCH v4 3/4] dt-bindings: PCI: rockchip: Add support for pcie wake irq

On Thu, Aug 24, 2017 at 11:53:54AM -0500, Bjorn Helgaas wrote: > On Tue, Aug 22, 2017 at 11:19:33AM +0800, Jeffy Chen wrote: > > Signed-off-by: Jeffy Chen > > diff --git a/Documentation/devicetree/bindings/pci/rockchip-pcie.txt > >

Re: [PATCH v4 3/4] dt-bindings: PCI: rockchip: Add support for pcie wake irq

On Thu, Aug 24, 2017 at 11:53:54AM -0500, Bjorn Helgaas wrote: > On Tue, Aug 22, 2017 at 11:19:33AM +0800, Jeffy Chen wrote: > > Signed-off-by: Jeffy Chen > > diff --git a/Documentation/devicetree/bindings/pci/rockchip-pcie.txt > > b/Documentation/devicetree/bindings/pci/rockchip-pcie.txt > >

Re: [PATCH] zram: add zstd to the supported algorithms list

On 8/24/17, 6:53 PM, "Sergey Senozhatsky" wrote: > On (08/25/17 01:35), Nick Terrell wrote: > > On 8/24/17, 5:49 PM, "Joonsoo Kim" wrote: > > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > > On Thu, Aug 24, 2017

Re: [PATCH] zram: add zstd to the supported algorithms list

On 8/24/17, 6:53 PM, "Sergey Senozhatsky" wrote: > On (08/25/17 01:35), Nick Terrell wrote: > > On 8/24/17, 5:49 PM, "Joonsoo Kim" wrote: > > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > > > > Add

  1   2   3   4   5   6   7   8   9   10   >