RE: [PATCH net-next 0/2] Add mqprio hardware offload support in hns3 driver

> Hi, Yuval > > On 2017/10/13 4:21, Yuval Mintz wrote: > >> This patchset adds a new hardware offload type in mqprio before adding > >> mqprio hardware offload support in hns3 driver. > > > > I think one of the biggest issues in tying this to DCB configuration is the > > non-immediate [and

RE: [PATCH net-next 0/2] Add mqprio hardware offload support in hns3 driver

> Hi, Yuval > > On 2017/10/13 4:21, Yuval Mintz wrote: > >> This patchset adds a new hardware offload type in mqprio before adding > >> mqprio hardware offload support in hns3 driver. > > > > I think one of the biggest issues in tying this to DCB configuration is the > > non-immediate [and

Hello dear

Good day dear, i hope this mail meets you well? my name is Jack, from the U.S. I know this may seem inappropriate so i ask for your forgiveness but i wish to get to know you better, if I may be so bold. I consider myself an easy-going man, adventurous, honest and fun loving person but I am

Hello dear

Good day dear, i hope this mail meets you well? my name is Jack, from the U.S. I know this may seem inappropriate so i ask for your forgiveness but i wish to get to know you better, if I may be so bold. I consider myself an easy-going man, adventurous, honest and fun loving person but I am

Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 3:48 PM, Kees Cook wrote: > On Sat, Oct 14, 2017 at 3:45 PM, Kees Cook wrote: >> On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik >> wrote: >>> Hi Kees, >>> >>> Today my linux-next build broke for the

Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 3:48 PM, Kees Cook wrote: > On Sat, Oct 14, 2017 at 3:45 PM, Kees Cook wrote: >> On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik >> wrote: >>> Hi Kees, >>> >>> Today my linux-next build broke for the pxa architecture. >>> My specific setup is : >>> - ARCH=arm make

[PATCH] Makefile: Another fix for stackprotector _AUTO mode

If the compiler didn't support a build mode, the second empty test would still trip. This moves it to an "else" test for the non-AUTO modes. Reported-by: Robert Jarzmik Signed-off-by: Kees Cook --- Robert, can you test this fix? --- Makefile | 7

[PATCH] Makefile: Another fix for stackprotector _AUTO mode

If the compiler didn't support a build mode, the second empty test would still trip. This moves it to an "else" test for the non-AUTO modes. Reported-by: Robert Jarzmik Signed-off-by: Kees Cook --- Robert, can you test this fix? --- Makefile | 7 --- 1 file changed, 4 insertions(+), 3

Re: [PATCH] arm64: KVM: set right LR register value for 32 bit guest when inject abort

Hi Marc, On 2017/10/13 23:12, Marc Zyngier wrote: > On 13/10/17 15:29, gengdongjiu wrote: >> Hi Marc, >> Thank you very much for your time to review it. >> >>> On 12/10/17 17:44, Dongjiu Geng wrote: When a exception is trapped to EL2, hardware uses ELR_ELx to hold the current fault

Re: [PATCH] arm64: KVM: set right LR register value for 32 bit guest when inject abort

Hi Marc, On 2017/10/13 23:12, Marc Zyngier wrote: > On 13/10/17 15:29, gengdongjiu wrote: >> Hi Marc, >> Thank you very much for your time to review it. >> >>> On 12/10/17 17:44, Dongjiu Geng wrote: When a exception is trapped to EL2, hardware uses ELR_ELx to hold the current fault

Re: [PATCH v5 03/10] kexec_file: factor out arch_kexec_kernel_*() from x86, powerpc

Hi AKASHI, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.14-rc4 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5 03/10] kexec_file: factor out arch_kexec_kernel_*() from x86, powerpc

Hi AKASHI, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.14-rc4 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 4/4] KVM: LAPIC: Don't silently accept bad vectors

2017-10-14 4:31 GMT+08:00 Radim Krčmář : > 2017-10-13 19:36+0200, Radim Krčmář: >> 2017-10-13 09:17+0800, Wanpeng Li: >> > 2017-10-04 22:44 GMT+08:00 Radim Krčmář : >> > > 2017-10-04 22:16+0800, Wanpeng Li: >> > >> 2017-10-04 20:01 GMT+08:00 Radim Krčmář

Re: [PATCH v2 4/4] KVM: LAPIC: Don't silently accept bad vectors

2017-10-14 4:31 GMT+08:00 Radim Krčmář : > 2017-10-13 19:36+0200, Radim Krčmář: >> 2017-10-13 09:17+0800, Wanpeng Li: >> > 2017-10-04 22:44 GMT+08:00 Radim Krčmář : >> > > 2017-10-04 22:16+0800, Wanpeng Li: >> > >> 2017-10-04 20:01 GMT+08:00 Radim Krčmář : >> > >> > 2017-10-04 15:56+0800, Wanpeng

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

From: Wanpeng Li According to the Intel SDM, volume 3, section 28.3.2: Creating and Using Cached Translation Information, "The following items describe the creation of mappings while EPT is not in use": - Linear mappings may be created. They are derived from the paging

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

From: Wanpeng Li According to the Intel SDM, volume 3, section 28.3.2: Creating and Using Cached Translation Information, "The following items describe the creation of mappings while EPT is not in use": - Linear mappings may be created. They are derived from the paging structures

[PATCH 1/2] KVM: VMX: Don't advertise EPT switching if EPT itself is not exposed

From: Wanpeng Li EPT switching is advertised unconditionally since it is emulated, however, it can be treated as an extended feature for EPT, it should be not advertised if EPT itself is not exposed. This patch fixes it. Cc: Paolo Bonzini Cc:

[PATCH 1/2] KVM: VMX: Don't advertise EPT switching if EPT itself is not exposed

From: Wanpeng Li EPT switching is advertised unconditionally since it is emulated, however, it can be treated as an extended feature for EPT, it should be not advertised if EPT itself is not exposed. This patch fixes it. Cc: Paolo Bonzini Cc: Radim Krčmář Signed-off-by: Wanpeng Li ---

Re: [PATCH] KVM: LAPIC: Level-sensitive interrupts are not support for LINT1

2017-10-14 4:43 GMT+08:00 Radim Krčmář : > 2017-10-12 21:27-0700, Wanpeng Li: >> From: Wanpeng Li >> >> SDM 10.5.1 mentioned: >> Software should always set the trigger mode in the LVT LINT1 register to 0 >> (edge >> sensitive). Level-sensitive

Re: [PATCH] KVM: LAPIC: Level-sensitive interrupts are not support for LINT1

2017-10-14 4:43 GMT+08:00 Radim Krčmář : > 2017-10-12 21:27-0700, Wanpeng Li: >> From: Wanpeng Li >> >> SDM 10.5.1 mentioned: >> Software should always set the trigger mode in the LVT LINT1 register to 0 >> (edge >> sensitive). Level-sensitive interrupts are not supported from LINT1. >> >> I

Re: [PATCH net-next,0/3] Add init of send table and var renames

From: Haiyang Zhang Date: Fri, 13 Oct 2017 12:28:02 -0700 > From: Haiyang Zhang > > Add initialization of send indirection table. Otherwise it may contain > old info of previous device with different number of channels. > > Also, did

Re: [PATCH net-next,0/3] Add init of send table and var renames

From: Haiyang Zhang Date: Fri, 13 Oct 2017 12:28:02 -0700 > From: Haiyang Zhang > > Add initialization of send indirection table. Otherwise it may contain > old info of previous device with different number of channels. > > Also, did some variable renaming for easier reading. Series applied,

Re: [PATCH][net-next] cxgb4: fix missing break in switch and indent return statements

From: Colin King Date: Fri, 13 Oct 2017 17:29:00 +0100 > From: Colin Ian King > > The break statement for the Macronix case is missing and will > fall through to the Winbond case and re-assign the size setting. > Fix this by adding the

Re: [PATCH][net-next] cxgb4: fix missing break in switch and indent return statements

From: Colin King Date: Fri, 13 Oct 2017 17:29:00 +0100 > From: Colin Ian King > > The break statement for the Macronix case is missing and will > fall through to the Winbond case and re-assign the size setting. > Fix this by adding the missing break statement. Also correctly > indent the

Re: [PATCH net-next v3 0/5] net: dsa: remove .set_addr

From: Vivien Didelot Date: Fri, 13 Oct 2017 14:18:04 -0400 > An Ethernet switch may support having a MAC address, which can be used > as the switch's source address in transmitted full-duplex Pause frames. > > If a DSA switch supports the related .set_addr

Re: [PATCH net-next v3 0/5] net: dsa: remove .set_addr

From: Vivien Didelot Date: Fri, 13 Oct 2017 14:18:04 -0400 > An Ethernet switch may support having a MAC address, which can be used > as the switch's source address in transmitted full-duplex Pause frames. > > If a DSA switch supports the related .set_addr operation, the DSA core > sets the

Re: [PATCH] atm: fore200e: mark expected switch fall-throughs

From: "Gustavo A. R. Silva" Date: Thu, 12 Oct 2017 16:11:32 -0500 > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Signed-off-by: Gustavo A. R. Silva Applied to net-next

Re: [PATCH] atm: fore200e: mark expected switch fall-throughs

From: "Gustavo A. R. Silva" Date: Thu, 12 Oct 2017 16:11:32 -0500 > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Signed-off-by: Gustavo A. R. Silva Applied to net-next

Re: [PATCH] fix typo in skbuff.c

From: Wenhua Shi Date: Sat, 14 Oct 2017 18:51:36 +0200 > --- > net/core/skbuff.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied, thanks.

Re: [PATCH] fix typo in skbuff.c

From: Wenhua Shi Date: Sat, 14 Oct 2017 18:51:36 +0200 > --- > net/core/skbuff.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied, thanks.

[rcu:rcu/next 30/45] include/linux/compiler.h:343:2: error: implicit declaration of function 'smp_read_barrier_depends'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next head: ea788e7da4886dff9782ad61d4c5e6ebadfa8260 commit: c3a030152f67ef977129c11e5b37a8e6071d4b6f [30/45] locking/barriers: Kill lockless_dereference config: sparc-alldefconfig (attached as .config) compiler:

[rcu:rcu/next 30/45] include/linux/compiler.h:343:2: error: implicit declaration of function 'smp_read_barrier_depends'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next head: ea788e7da4886dff9782ad61d4c5e6ebadfa8260 commit: c3a030152f67ef977129c11e5b37a8e6071d4b6f [30/45] locking/barriers: Kill lockless_dereference config: sparc-alldefconfig (attached as .config) compiler:

Re: [PATCH] nullb: make config_item_type const

Hi Bhumika, [auto build test WARNING on linus/master] [also build test WARNING on v4.14-rc4 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] nullb: make config_item_type const

Hi Bhumika, [auto build test WARNING on linus/master] [also build test WARNING on v4.14-rc4 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V10 0/8] blk-mq-sched: improve sequential I/O performance

On Sat, Oct 14, 2017 at 09:39:21AM -0600, Jens Axboe wrote: > On 10/14/2017 03:22 AM, Ming Lei wrote: > > Hi Jens, > > > > In Red Hat internal storage test wrt. blk-mq scheduler, we found that I/O > > performance is much bad with mq-deadline, especially about sequential I/O > > on some

Re: [PATCH V10 0/8] blk-mq-sched: improve sequential I/O performance

On Sat, Oct 14, 2017 at 09:39:21AM -0600, Jens Axboe wrote: > On 10/14/2017 03:22 AM, Ming Lei wrote: > > Hi Jens, > > > > In Red Hat internal storage test wrt. blk-mq scheduler, we found that I/O > > performance is much bad with mq-deadline, especially about sequential I/O > > on some

Re: [PATCH V10 0/8] blk-mq-sched: improve sequential I/O performance

On Sat, Oct 14, 2017 at 07:38:29PM +0200, Oleksandr Natalenko wrote: > Hi. > > By any chance, could this be backported to 4.14? I'm confused with "SCSI: > allow to pass null rq to scsi_prep_state_check()" since it uses refactored > flags. > > === > if (req && !(req->rq_flags & RQF_PREEMPT)) >

Re: [PATCH V10 0/8] blk-mq-sched: improve sequential I/O performance

On Sat, Oct 14, 2017 at 07:38:29PM +0200, Oleksandr Natalenko wrote: > Hi. > > By any chance, could this be backported to 4.14? I'm confused with "SCSI: > allow to pass null rq to scsi_prep_state_check()" since it uses refactored > flags. > > === > if (req && !(req->rq_flags & RQF_PREEMPT)) >

Re: [PATCH] Add -target to clang switch while cross compiling.

On 10/13/2017 09:24 PM, Abhijit Ayarekar wrote: Update to llvm excludes assembly instructions. llvm git revision is below commit 65fad7c26569 ("bpf: add inline-asm support") This change will be part of llvm release 6.0 __ASM_SYSREG_H define is not required for native compile. -target switch

Re: [PATCH] Add -target to clang switch while cross compiling.

On 10/13/2017 09:24 PM, Abhijit Ayarekar wrote: Update to llvm excludes assembly instructions. llvm git revision is below commit 65fad7c26569 ("bpf: add inline-asm support") This change will be part of llvm release 6.0 __ASM_SYSREG_H define is not required for native compile. -target switch

Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 3:45 PM, Kees Cook wrote: > On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik > wrote: >> Hi Kees, >> >> Today my linux-next build broke for the pxa architecture. >> My specific setup is : >> - ARCH=arm make pxa_defconfig;

Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 3:45 PM, Kees Cook wrote: > On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik > wrote: >> Hi Kees, >> >> Today my linux-next build broke for the pxa architecture. >> My specific setup is : >> - ARCH=arm make pxa_defconfig; ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- >>

Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik wrote: > Hi Kees, > > Today my linux-next build broke for the pxa architecture. > My specific setup is : > - ARCH=arm make pxa_defconfig; ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make > - my compiler is: >

Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik wrote: > Hi Kees, > > Today my linux-next build broke for the pxa architecture. > My specific setup is : > - ARCH=arm make pxa_defconfig; ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make > - my compiler is: >

Re: [OpenWrt-Devel] [PATCH v3 0/6] staging: Introduce DPAA2 Ethernet Switch driver

On October 14, 2017 2:59:22 PM PDT, Linus Walleij wrote: >On Sat, Oct 14, 2017 at 8:52 PM, Florian Fainelli > wrote: > >> The most deployed switch device drivers have been converted to DSA >> already: b53, qca8k (ar83xx in OpenWrt/LEDE) and mtk7530

Re: [OpenWrt-Devel] [PATCH v3 0/6] staging: Introduce DPAA2 Ethernet Switch driver

On October 14, 2017 2:59:22 PM PDT, Linus Walleij wrote: >On Sat, Oct 14, 2017 at 8:52 PM, Florian Fainelli > wrote: > >> The most deployed switch device drivers have been converted to DSA >> already: b53, qca8k (ar83xx in OpenWrt/LEDE) and mtk7530 are all in >> tree, and now we are getting new

Re: [OpenWrt-Devel] [PATCH v3 0/6] staging: Introduce DPAA2 Ethernet Switch driver

On Sat, Oct 14, 2017 at 8:52 PM, Florian Fainelli wrote: > The most deployed switch device drivers have been converted to DSA > already: b53, qca8k (ar83xx in OpenWrt/LEDE) and mtk7530 are all in > tree, and now we are getting new submissions from Michrochip to support >

Re: [OpenWrt-Devel] [PATCH v3 0/6] staging: Introduce DPAA2 Ethernet Switch driver

On Sat, Oct 14, 2017 at 8:52 PM, Florian Fainelli wrote: > The most deployed switch device drivers have been converted to DSA > already: b53, qca8k (ar83xx in OpenWrt/LEDE) and mtk7530 are all in > tree, and now we are getting new submissions from Michrochip to support > their pretty large KSZ

[PATCH v3 RESEND] cpufreq: pxa: convert to clock API

As the clock settings have been introduced into the clock pxa drivers, which are now available to change the CPU clock by themselves, remove the clock handling from this driver, and rely on pxa clock drivers. Signed-off-by: Robert Jarzmik Acked-by: Viresh Kumar

[PATCH v3 RESEND] cpufreq: pxa: convert to clock API

As the clock settings have been introduced into the clock pxa drivers, which are now available to change the CPU clock by themselves, remove the clock handling from this driver, and rely on pxa clock drivers. Signed-off-by: Robert Jarzmik Acked-by: Viresh Kumar --- This is a resend of a

Re: [PATCH] parisc: parport_gsc: constify parisc_device_id

On Sat, Aug 19, 2017 at 10:38:41PM +0530, Arvind Yadav wrote: > parisc_device_id are not supposed to change at runtime. All functions > working with parisc_device_id provided by work > with > const parisc_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [PATCH] parisc: parport_gsc: constify parisc_device_id

On Sat, Aug 19, 2017 at 10:38:41PM +0530, Arvind Yadav wrote: > parisc_device_id are not supposed to change at runtime. All functions > working with parisc_device_id provided by work > with > const parisc_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav > --- >

[PATCH] drm/tinydrm: Replace list_for_each with list_for_each_entry

Replace use of list_for_each with list_for_each_entry to simplify the code and remove variables that are used only in list_for_each. Done with following coccinelle patch: @r@ identifier fn,i,f,p; expression e; iterator name list_for_each, list_for_each_entry; type T; @@ fn(...) { ++ T *i;

[PATCH] drm/tinydrm: Replace list_for_each with list_for_each_entry

Replace use of list_for_each with list_for_each_entry to simplify the code and remove variables that are used only in list_for_each. Done with following coccinelle patch: @r@ identifier fn,i,f,p; expression e; iterator name list_for_each, list_for_each_entry; type T; @@ fn(...) { ++ T *i;

Re: [PATCH for linux-next] mm/page-writeback.c: make changes of dirty_writeback_centisecs take effect immediately

On 10/14/2017 11:59 AM, Damian Tometzki wrote: > On Sat, 14. Oct 16:38, Yafang Shao wrote: >> This patch is the followup of the prvious patch: >> [writeback: schedule periodic writeback with sysctl]. >> >> There's another issue to fix. >> For example, >> - When the tunable was set to one hour and

Re: [PATCH for linux-next] mm/page-writeback.c: make changes of dirty_writeback_centisecs take effect immediately

On 10/14/2017 11:59 AM, Damian Tometzki wrote: > On Sat, 14. Oct 16:38, Yafang Shao wrote: >> This patch is the followup of the prvious patch: >> [writeback: schedule periodic writeback with sysctl]. >> >> There's another issue to fix. >> For example, >> - When the tunable was set to one hour and

Re: [PATCH 2/2] kbuild: redefine __FILE__ as relative path from $(srctree) if possible

Hi Masahiro, [auto build test WARNING on mmarek/for-next] [also build test WARNING on next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 2/2] kbuild: redefine __FILE__ as relative path from $(srctree) if possible

Hi Masahiro, [auto build test WARNING on mmarek/for-next] [also build test WARNING on next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 RFC 7/7] Modify tag_ksz.c so that tail tag code can be used by other KSZ switch drivers

On Fri, Oct 06, 2017 at 01:33:05PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Modify tag_ksz.c so that tail tag code can be used by other KSZ switch > drivers. There is multiple things going on in this patch. Please split the special_mult_addr

Re: [PATCH v1 RFC 7/7] Modify tag_ksz.c so that tail tag code can be used by other KSZ switch drivers

On Fri, Oct 06, 2017 at 01:33:05PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Modify tag_ksz.c so that tail tag code can be used by other KSZ switch > drivers. There is multiple things going on in this patch. Please split the special_mult_addr change into a separate patch,

[PATCH] ASoC: wm97xx: fix compilation corner case

When the old AC97 is not used, CONFIG_SND_SOC_AC97_BUS is not defined. As a consequence, in the error path, snd_soc_free_ac97_codec() is not defined and triggers a compilation error. Fix it for wm9705 and wm9712, as wm9713 is correctly written. Signed-off-by: Robert Jarzmik

[PATCH] ASoC: wm97xx: fix compilation corner case

When the old AC97 is not used, CONFIG_SND_SOC_AC97_BUS is not defined. As a consequence, in the error path, snd_soc_free_ac97_codec() is not defined and triggers a compilation error. Fix it for wm9705 and wm9712, as wm9713 is correctly written. Signed-off-by: Robert Jarzmik ---

[PATCH] drm/omap: Replace list_for_each with list_for_each_entry

Replace use of list_for_each with list_for_each_entry to simplify the code and remove variables that are used only in list_for_each. Done with following coccinelle patch: @r@ identifier fn,i,f,p; expression e; iterator name list_for_each, list_for_each_entry; type T; @@ fn(...) { ++ T *i;

[PATCH] drm/omap: Replace list_for_each with list_for_each_entry

Replace use of list_for_each with list_for_each_entry to simplify the code and remove variables that are used only in list_for_each. Done with following coccinelle patch: @r@ identifier fn,i,f,p; expression e; iterator name list_for_each, list_for_each_entry; type T; @@ fn(...) { ++ T *i;

Re: [PATCH v1 RFC 6/7] Add MIB counter reading support

> +static void ksz9477_phy_setup(struct ksz_device *dev, int port, > + struct phy_device *phy) > +{ > + if (port < dev->phy_port_cnt) { > + /* SUPPORTED_Asym_Pause and SUPPORTED_Pause can be removed to > + * disable flow control when rate

Re: [PATCH v1 RFC 6/7] Add MIB counter reading support

> +static void ksz9477_phy_setup(struct ksz_device *dev, int port, > + struct phy_device *phy) > +{ > + if (port < dev->phy_port_cnt) { > + /* SUPPORTED_Asym_Pause and SUPPORTED_Pause can be removed to > + * disable flow control when rate

Stack protector kernel build error

Hi Kees, Today my linux-next build broke for the pxa architecture. My specific setup is : - ARCH=arm make pxa_defconfig; ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make - my compiler is: rj@belgarion:~/mio_linux/kernel$ arm-linux-gnueabi-gcc --version arm-linux-gnueabi-gcc

Stack protector kernel build error

Hi Kees, Today my linux-next build broke for the pxa architecture. My specific setup is : - ARCH=arm make pxa_defconfig; ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make - my compiler is: rj@belgarion:~/mio_linux/kernel$ arm-linux-gnueabi-gcc --version arm-linux-gnueabi-gcc

Re: [PATCH v1 RFC 5/7] Break KSZ9477 DSA driver into two files

> diff --git a/drivers/net/dsa/microchip/ksz9477.c > b/drivers/net/dsa/microchip/ksz9477.c > new file mode 100644 > index 000..214d380 > --- /dev/null > +++ b/drivers/net/dsa/microchip/ksz9477.c > @@ -0,0 +1,1328 @@ > +/* > + * Microchip KSZ9477 switch driver main logic > + * > + * Copyright

Re: [PATCH v1 RFC 5/7] Break KSZ9477 DSA driver into two files

> diff --git a/drivers/net/dsa/microchip/ksz9477.c > b/drivers/net/dsa/microchip/ksz9477.c > new file mode 100644 > index 000..214d380 > --- /dev/null > +++ b/drivers/net/dsa/microchip/ksz9477.c > @@ -0,0 +1,1328 @@ > +/* > + * Microchip KSZ9477 switch driver main logic > + * > + * Copyright

Re: Documentation: add Kernel Driver Statement to the kernel

On Sat, Oct 14, 2017 at 08:09:59PM +0200, Wolfram Sang wrote: > > > Not that sphinx doesn't have it's own issues, but you have to admit it > > is much better now than it used to be, right? > > That goes without saying, but we still added plain textfiles to > Documentation/ since 2008, so I was

Re: Documentation: add Kernel Driver Statement to the kernel

On Sat, Oct 14, 2017 at 08:09:59PM +0200, Wolfram Sang wrote: > > > Not that sphinx doesn't have it's own issues, but you have to admit it > > is much better now than it used to be, right? > > That goes without saying, but we still added plain textfiles to > Documentation/ since 2008, so I was

Re: [PATCH v1 RFC 4/7] Rename ksz_spi.c to ksz9477_spi.c

On Fri, Oct 06, 2017 at 01:33:02PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Rename ksz_spi.c to ksz9477_spi.c and update Kconfig in preparation to add > more KSZ switch drivers. > > Signed-off-by: Tristram Ha

Re: [PATCH v1 RFC 4/7] Rename ksz_spi.c to ksz9477_spi.c

On Fri, Oct 06, 2017 at 01:33:02PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Rename ksz_spi.c to ksz9477_spi.c and update Kconfig in preparation to add > more KSZ switch drivers. > > Signed-off-by: Tristram Ha Reviewed-by: Andrew Lunn Andrew

Re: [PATCH v1 RFC 3/7] Rename some functions with ksz9477 prefix

On Fri, Oct 06, 2017 at 01:33:01PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Rename some functions with ksz9477 prefix to separate chip specific code > from common code. > > Signed-off-by: Tristram Ha Reviewed-by:

Re: [PATCH v1 RFC 3/7] Rename some functions with ksz9477 prefix

On Fri, Oct 06, 2017 at 01:33:01PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Rename some functions with ksz9477 prefix to separate chip specific code > from common code. > > Signed-off-by: Tristram Ha Reviewed-by: Andrew Lunn Andrew

Re: [PATCH v1 RFC 2/7] Clean up code according to patch check suggestions

On Fri, Oct 06, 2017 at 01:33:00PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Clean up code according to patch check suggestions. > > Signed-off-by: Tristram Ha Reviewed-by: Andrew Lunn Andrew

Re: [PATCH v1 RFC 1/7] Replace license with GPL

On Mon, Oct 09, 2017 at 09:18:16AM +, David Laight wrote: > From: tristram...@microchip.com > > Sent: 06 October 2017 21:33 > > Replace license with GPL. > > Don't you need permission from all the people who have updated > the files in order to make this change? Hi David Interesting

Re: [PATCH v1 RFC 2/7] Clean up code according to patch check suggestions

On Fri, Oct 06, 2017 at 01:33:00PM -0700, tristram...@microchip.com wrote: > From: Tristram Ha > > Clean up code according to patch check suggestions. > > Signed-off-by: Tristram Ha Reviewed-by: Andrew Lunn Andrew

Re: [PATCH v1 RFC 1/7] Replace license with GPL

On Mon, Oct 09, 2017 at 09:18:16AM +, David Laight wrote: > From: tristram...@microchip.com > > Sent: 06 October 2017 21:33 > > Replace license with GPL. > > Don't you need permission from all the people who have updated > the files in order to make this change? Hi David Interesting

Re: [PATCH v4 3/4] platform/chrome: Add cros_ec_accel_legacy driver

On Thu, 12 Oct 2017 19:33:23 +0200 Thierry Escande wrote: > From: Gwendal Grignou > > Add driver to support older EC firmware that only support deprecated > ec command. Rely on ACPI memory map register to access sensor > information. >

Re: [PATCH v4 3/4] platform/chrome: Add cros_ec_accel_legacy driver

On Thu, 12 Oct 2017 19:33:23 +0200 Thierry Escande wrote: > From: Gwendal Grignou > > Add driver to support older EC firmware that only support deprecated > ec command. Rely on ACPI memory map register to access sensor > information. > Present same interface as the regular cros_ec sensor

Re: [PATCH v5 11/16] perf report: properly handle branch count in match_chain

On Freitag, 13. Oktober 2017 16:08:34 CEST Arnaldo Carvalho de Melo wrote: > Em Fri, Oct 13, 2017 at 10:39:03AM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Mon, Oct 09, 2017 at 10:33:05PM +0200, Milian Wolff escreveu: > > > Some of the code paths I introduced before returned too early > > >

Re: [PATCH v5 11/16] perf report: properly handle branch count in match_chain

On Freitag, 13. Oktober 2017 16:08:34 CEST Arnaldo Carvalho de Melo wrote: > Em Fri, Oct 13, 2017 at 10:39:03AM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Mon, Oct 09, 2017 at 10:33:05PM +0200, Milian Wolff escreveu: > > > Some of the code paths I introduced before returned too early > > >

Re: [PATCH] netconsole: make config_item_type const

Hi Bhumika, [auto build test WARNING on net-next/master] [also build test WARNING on v4.14-rc4 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] netconsole: make config_item_type const

Hi Bhumika, [auto build test WARNING on net-next/master] [also build test WARNING on v4.14-rc4 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/1] arm64: dts: rockchip: default serial for Firefly-RK3399

Am Samstag, 30. September 2017, 06:06:40 CEST schrieb Heinrich Schuchardt: > The Firefly-RK3399 uses serial2 with 1,500,000 baud by default > for communication in U-Boot and in the vendor provided distros. > > So let us set the same default in the Linux kernel. > > Signed-off-by: Heinrich

Re: [PATCH 1/1] arm64: dts: rockchip: default serial for Firefly-RK3399

Am Samstag, 30. September 2017, 06:06:40 CEST schrieb Heinrich Schuchardt: > The Firefly-RK3399 uses serial2 with 1,500,000 baud by default > for communication in U-Boot and in the vendor provided distros. > > So let us set the same default in the Linux kernel. > > Signed-off-by: Heinrich

Re: [PATCH] arm64: dts: rockchip: enable touchpad button for rk3399-gru-kevin

Am Montag, 9. Oktober 2017, 20:40:28 CEST schrieb Emil Renner Berthing: > Adding the linux,gpio-keymap entry also has > the side-effect of making the driver register > the touchpad as a touchpad rather than another > touchscreen. > > The index for BTN_LEFT was found by trial and error. > >

Re: [PATCH] arm64: dts: rockchip: enable touchpad button for rk3399-gru-kevin

Am Montag, 9. Oktober 2017, 20:40:28 CEST schrieb Emil Renner Berthing: > Adding the linux,gpio-keymap entry also has > the side-effect of making the driver register > the touchpad as a touchpad rather than another > touchscreen. > > The index for BTN_LEFT was found by trial and error. > >

Re: [PATCH] ARM: dts: rockchip: Enable thermal on rk3288-vyasa board

Am Freitag, 13. Oktober 2017, 23:03:32 CEST schrieb Jagan Teki: > From: Michael Trimarchi > > Enable thermal on rk3288-vyasa board, TSHUT is high active. > > Signed-off-by: Michael Trimarchi > Signed-off-by: Jagan Teki

Re: [PATCH] ARM: dts: rockchip: Enable thermal on rk3288-vyasa board

Am Freitag, 13. Oktober 2017, 23:03:32 CEST schrieb Jagan Teki: > From: Michael Trimarchi > > Enable thermal on rk3288-vyasa board, TSHUT is high active. > > Signed-off-by: Michael Trimarchi > Signed-off-by: Jagan Teki applied for 4.15 Thanks Heiko

[PATCH] net/rose: Delete an error message for a failed memory allocation in rose_proto_init()

From: Markus Elfring Date: Sat, 14 Oct 2017 20:57:28 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] net/rose: Delete an error message for a failed memory allocation in rose_proto_init()

From: Markus Elfring Date: Sat, 14 Oct 2017 20:57:28 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- net/rose/af_rose.c | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [PATCH] iio: adc: at91-sama5d2_adc: fix probe error on missing trigger property

On Wed, 11 Oct 2017 14:21:14 +0300 Eugen Hristev wrote: > This fix allows platforms to probe correctly even if the > trigger edge property is missing. The hardware trigger > will no longer be registered in the sybsystem > Preserves backwards compatibility with the

Re: [PATCH] iio: adc: at91-sama5d2_adc: fix probe error on missing trigger property

On Wed, 11 Oct 2017 14:21:14 +0300 Eugen Hristev wrote: > This fix allows platforms to probe correctly even if the > trigger edge property is missing. The hardware trigger > will no longer be registered in the sybsystem > Preserves backwards compatibility with the support that > was in the

Re: [OpenWrt-Devel] [PATCH v3 0/6] staging: Introduce DPAA2 Ethernet Switch driver

Hi, On 10/14/2017 04:09 AM, Linus Walleij wrote: > Top posting and resending since net...@vger.kernel.org > is the right mail address for this. Mea culpa. > > Linus Walleij > > On Sat, Oct 14, 2017 at 11:35 AM, Linus Walleij > wrote: >> On Thu, Oct 5, 2017 at 11:16

Re: [OpenWrt-Devel] [PATCH v3 0/6] staging: Introduce DPAA2 Ethernet Switch driver

Hi, On 10/14/2017 04:09 AM, Linus Walleij wrote: > Top posting and resending since net...@vger.kernel.org > is the right mail address for this. Mea culpa. > > Linus Walleij > > On Sat, Oct 14, 2017 at 11:35 AM, Linus Walleij > wrote: >> On Thu, Oct 5, 2017 at 11:16 AM, Razvan Stefanescu >>

[PATCH v5] drm/i915: Replace *_reference/unreference() or *_ref/unref with _get/put()

Replace instances of drm_framebuffer_reference/unreference() with *_get/put() suffixes and drm_dev_unref with *_put() suffix because get/put is shorter and consistent with the kernel use of *_get/put suffixes. Done with following coccinelle semantic patch @@ expression ex; @@ (

[PATCH v5] drm/i915: Replace *_reference/unreference() or *_ref/unref with _get/put()

Replace instances of drm_framebuffer_reference/unreference() with *_get/put() suffixes and drm_dev_unref with *_put() suffix because get/put is shorter and consistent with the kernel use of *_get/put suffixes. Done with following coccinelle semantic patch @@ expression ex; @@ (

  1   2   3   4   5   >