Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, Mar 23, 2017 at 9:27 PM, Eric Dumazet wrote: > On Thu, 2017-03-23 at 20:42 -0700, Alexander Duyck wrote: >> On Thu, Mar 23, 2017 at 6:24 PM, Eric Dumazet wrote: >> > On Thu, 2017-03-23 at 14:37 -0700, Alexander Duyck wrote: >> >> From:

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, Mar 23, 2017 at 9:27 PM, Eric Dumazet wrote: > On Thu, 2017-03-23 at 20:42 -0700, Alexander Duyck wrote: >> On Thu, Mar 23, 2017 at 6:24 PM, Eric Dumazet wrote: >> > On Thu, 2017-03-23 at 14:37 -0700, Alexander Duyck wrote: >> >> From: Alexander Duyck >> >> >> > >> >> The last bit I

[PATCH] drivers/staging/media: atomisp: Removing redundant information from dev_err

Removing hardcoded function name as code is already using __func__ Signed-off-by: Pushkar Jambhlekar --- drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm_bo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] drivers/staging/media: atomisp: Removing redundant information from dev_err

Removing hardcoded function name as code is already using __func__ Signed-off-by: Pushkar Jambhlekar --- drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm_bo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm_bo.c

[PATCH v4 2/2] fpga: Add support for Xilinx LogiCORE PR Decoupler

This adds support for the Xilinx LogiCORE PR Decoupler soft-ip that does decoupling of PR regions in the FPGA fabric during partial reconfiguration. Signed-off-by: Moritz Fischer Signed-off-by: Michal Simek Cc: Sören Brinkmann

[PATCH v4 1/2] doc: Add bindings document for Xilinx LogiCore PR Decoupler

This adds the binding documentation for the Xilinx LogiCORE PR Decoupler soft core. Signed-off-by: Moritz Fischer Signed-off-by: Michal Simek Acked-by: Alan Tull Cc: Sören Brinkmann Cc:

[PATCH v4 2/2] fpga: Add support for Xilinx LogiCORE PR Decoupler

This adds support for the Xilinx LogiCORE PR Decoupler soft-ip that does decoupling of PR regions in the FPGA fabric during partial reconfiguration. Signed-off-by: Moritz Fischer Signed-off-by: Michal Simek Cc: Sören Brinkmann Cc: linux-kernel@vger.kernel.org Cc: devicet...@vger.kernel.org ---

[PATCH v4 1/2] doc: Add bindings document for Xilinx LogiCore PR Decoupler

This adds the binding documentation for the Xilinx LogiCORE PR Decoupler soft core. Signed-off-by: Moritz Fischer Signed-off-by: Michal Simek Acked-by: Alan Tull Cc: Sören Brinkmann Cc: linux-kernel@vger.kernel.org Cc: devicet...@vger.kernel.org --- Changes from v3: - Addressed Michal's

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

Hi all, Today's linux-next merge of the akpm tree got a conflict in: arch/x86/include/asm/atomic.h between commit: e6790e4b5d5e ("locking/atomic/x86: Use atomic_try_cmpxchg()") from the tip tree and patch: "x86/atomic: move __arch_atomic_add_unless out of line" from the akpm tree. I

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

Hi all, Today's linux-next merge of the akpm tree got a conflict in: arch/x86/include/asm/atomic.h between commit: e6790e4b5d5e ("locking/atomic/x86: Use atomic_try_cmpxchg()") from the tip tree and patch: "x86/atomic: move __arch_atomic_add_unless out of line" from the akpm tree. I

Re: [v1 8/9] x86/tsc: tsc early

Hi Pavel, [auto build test ERROR on tip/sched/core] [also build test ERROR on v4.11-rc3 next-20170323] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Pavel

Re: [v1 8/9] x86/tsc: tsc early

Hi Pavel, [auto build test ERROR on tip/sched/core] [also build test ERROR on v4.11-rc3 next-20170323] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Pavel

Re: [PATCH] x86/boot: Support uncompressed kernel

> > > The patch adds a 'CONFIG_KERNEL_RAW' configure choice so the built > > > binary > > > can have no uncompressing at all. The experiment shows: > > > > > > kernel   kernel sizetime in decompress_kernel > > > compressed (gzip)3.3M   53ms > > >

Re: [PATCH] x86/boot: Support uncompressed kernel

> > > The patch adds a 'CONFIG_KERNEL_RAW' configure choice so the built > > > binary > > > can have no uncompressing at all. The experiment shows: > > > > > > kernel   kernel sizetime in decompress_kernel > > > compressed (gzip)3.3M   53ms > > >

[PATCH v2 0/2] serial: Add name field to uart_port

This series adds name attribute to uart_port struct inorder to store name of the tty port that will help in identify different uart instances. This patch series is based on discussion here[1]. [1] https://www.spinics.net/lists/arm-kernel/msg569188.html Previous version:

[PATCH v2 0/2] serial: Add name field to uart_port

This series adds name attribute to uart_port struct inorder to store name of the tty port that will help in identify different uart instances. This patch series is based on discussion here[1]. [1] https://www.spinics.net/lists/arm-kernel/msg569188.html Previous version:

[PATCH v2 1/2] tty: serial_core: Add name field to uart_port struct

Introduce a field to store name of uart_port that can be used to easily identify UART port instances on a system that has more than one UART instance. The name is of the form ttyXN(eg. ttyS0, ttyAMA0,..) where N is number that particular UART instance. This field will be useful when printing debug

[PATCH v2 1/2] tty: serial_core: Add name field to uart_port struct

Introduce a field to store name of uart_port that can be used to easily identify UART port instances on a system that has more than one UART instance. The name is of the form ttyXN(eg. ttyS0, ttyAMA0,..) where N is number that particular UART instance. This field will be useful when printing debug

[PATCH v2 2/2] serial: 8250: 8250_core: Fix irq name for 8250 serial IRQ

Using dev_name() as IRQ name during request_irq() might be misleading in case of serial over PCI. Therefore identify serial port IRQ using uart_port's name field. This will help mapping IRQs to appropriate ttySN(where N is the serial port index) instances. Signed-off-by: Vignesh R

[PATCH v2 2/2] serial: 8250: 8250_core: Fix irq name for 8250 serial IRQ

Using dev_name() as IRQ name during request_irq() might be misleading in case of serial over PCI. Therefore identify serial port IRQ using uart_port's name field. This will help mapping IRQs to appropriate ttySN(where N is the serial port index) instances. Signed-off-by: Vignesh R Reviewed-by:

[PATCH] drivers/video/fbdev: Fixing coding guidelines in acornfb.c

Fixing coding guidelines error reported by 'checkpatch.pl' Signed-off-by: Pushkar Jambhlekar --- drivers/video/fbdev/acornfb.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/drivers/video/fbdev/acornfb.c b/drivers/video/fbdev/acornfb.c

[PATCH] drivers/video/fbdev: Fixing coding guidelines in acornfb.c

Fixing coding guidelines error reported by 'checkpatch.pl' Signed-off-by: Pushkar Jambhlekar --- drivers/video/fbdev/acornfb.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/drivers/video/fbdev/acornfb.c b/drivers/video/fbdev/acornfb.c index fb75b7e..0c325b4

linux-next: manual merge of the akpm-current tree with the tip tree

Hi all, Today's linux-next merge of the akpm-current tree got conflicts in: arch/x86/include/asm/atomic.h arch/x86/include/asm/atomic64_64.h between commits: a9ebf306f52c ("locking/atomic: Introduce atomic_try_cmpxchg()") e6790e4b5d5e ("locking/atomic/x86: Use atomic_try_cmpxchg()")

linux-next: manual merge of the akpm-current tree with the tip tree

Hi all, Today's linux-next merge of the akpm-current tree got conflicts in: arch/x86/include/asm/atomic.h arch/x86/include/asm/atomic64_64.h between commits: a9ebf306f52c ("locking/atomic: Introduce atomic_try_cmpxchg()") e6790e4b5d5e ("locking/atomic/x86: Use atomic_try_cmpxchg()")

Re: [PATCH 07/12] ARM: dts: imx6ul-isiot: Add Sound card with codec node

On Wed, Mar 22, 2017 at 11:18:12PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Add support for Sound card and related codec(via i2c1) nodes > on Engicam Is.IoT MX6UL variant module boards. > > Cc: Shawn Guo > Cc: Matteo Lisi

Re: [PATCH 07/12] ARM: dts: imx6ul-isiot: Add Sound card with codec node

On Wed, Mar 22, 2017 at 11:18:12PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Add support for Sound card and related codec(via i2c1) nodes > on Engicam Is.IoT MX6UL variant module boards. > > Cc: Shawn Guo > Cc: Matteo Lisi > Cc: Michael Trimarchi > Signed-off-by: Jagan Teki > --- >

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

On (03/23/17 11:40), Petr Mladek wrote: [..] > Let me do one more attempt for a generic name. What about? > > printk_console_press();or try_harder() or push() > printk_console_relax(); > > or something like this? I replied in another thread. how about printk_rescue? -ss

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

On (03/23/17 11:40), Petr Mladek wrote: [..] > Let me do one more attempt for a generic name. What about? > > printk_console_press();or try_harder() or push() > printk_console_relax(); > > or something like this? I replied in another thread. how about printk_rescue? -ss

Re: [PATCH 00/12] ARM: dts: i.MX6: Add lcdif/sound nodes on Engicam SOMs

On Wed, Mar 22, 2017 at 11:18:05PM +0530, Jagan Teki wrote: > From: Jagan Teki > > This patchset, add support for backlight, lcdif, touchscreen, > sound card and related codec and can nodes all Engicam SOM's > which are supporting mainline as of now. Per MAINTAINERS,

Re: [PATCH 00/12] ARM: dts: i.MX6: Add lcdif/sound nodes on Engicam SOMs

On Wed, Mar 22, 2017 at 11:18:05PM +0530, Jagan Teki wrote: > From: Jagan Teki > > This patchset, add support for backlight, lcdif, touchscreen, > sound card and related codec and can nodes all Engicam SOM's > which are supporting mainline as of now. Per MAINTAINERS, you should copy Sascha

Re: [PATCH 05/12] ARM: dts: imx6ul-isiot-common: Add touchscreen node

On Wed, Mar 22, 2017 at 11:18:10PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Add touchscreen node as i2c1 slave device on Engicam Is.IoT MX6UL > modules, the touchscreen controlled 'st,stmpe-ts' connected via > i2c with st,stmpe811 mfb interface. s/mfb/mfd? >

Re: [PATCH 05/12] ARM: dts: imx6ul-isiot-common: Add touchscreen node

On Wed, Mar 22, 2017 at 11:18:10PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Add touchscreen node as i2c1 slave device on Engicam Is.IoT MX6UL > modules, the touchscreen controlled 'st,stmpe-ts' connected via > i2c with st,stmpe811 mfb interface. s/mfb/mfd? > > Cc: Shawn Guo > Cc:

Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID

On Thu, Mar 23, 2017 at 9:47 PM, Andy Lutomirski wrote: > So don't we want queue id, not NAPI id? Or am I still missing something? > > But I'm also a but confused as to the overall performance effect. > Suppose I have an rx queue that has its interrupt bound to cpu 0. For >

Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID

On Thu, Mar 23, 2017 at 9:47 PM, Andy Lutomirski wrote: > So don't we want queue id, not NAPI id? Or am I still missing something? > > But I'm also a but confused as to the overall performance effect. > Suppose I have an rx queue that has its interrupt bound to cpu 0. For > whatever reason

[PATCH v2] x86/mm/KASLR: EFI region is mistakenly included into KASLR VA space for randomization

Currently KASLR is enabled on three regions: the direct mapping of physical memory, vamlloc and vmemmap. However EFI region is also mistakenly included for VA space randomization because of misusing EFI_VA_START macro and assuming EFI_VA_START < EFI_VA_END. The EFI region is reserved for EFI

[PATCH v2] x86/mm/KASLR: EFI region is mistakenly included into KASLR VA space for randomization

Currently KASLR is enabled on three regions: the direct mapping of physical memory, vamlloc and vmemmap. However EFI region is also mistakenly included for VA space randomization because of misusing EFI_VA_START macro and assuming EFI_VA_START < EFI_VA_END. The EFI region is reserved for EFI

Re: [PATCH] ASoC: WM8962: Let codec driver enable/disable its MCLK

On Thu, Mar 23, 2017 at 02:01:50PM +0200, Daniel Baluta wrote: > From: Nicolin Chen > > WM8962 needs its MCLK when powerup in wm8962_resume(). Thus it's better > to control the MCLK in codec driver. Thus remove the clock enable in > machine dirver accordingly. > > While at

Re: [PATCH] ASoC: WM8962: Let codec driver enable/disable its MCLK

On Thu, Mar 23, 2017 at 02:01:50PM +0200, Daniel Baluta wrote: > From: Nicolin Chen > > WM8962 needs its MCLK when powerup in wm8962_resume(). Thus it's better > to control the MCLK in codec driver. Thus remove the clock enable in > machine dirver accordingly. > > While at it, get rid of

Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure

John Hubbard writes: > On 03/23/2017 07:41 PM, Huang, Ying wrote: >> David Rientjes writes: >> >>> On Mon, 20 Mar 2017, Huang, Ying wrote: >>> From: Huang Ying Now vzalloc() is used in swap code to allocate various

Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure

John Hubbard writes: > On 03/23/2017 07:41 PM, Huang, Ying wrote: >> David Rientjes writes: >> >>> On Mon, 20 Mar 2017, Huang, Ying wrote: >>> From: Huang Ying Now vzalloc() is used in swap code to allocate various data structures, such as swap cache, swap slots cache,

Re: [PATCH] ASoC: WM8962: Let codec driver enable/disable its MCLK

Hi, Could you please revise the subject a bit? I forgot what's the original one I submitted (internally) years ago. But the patch is for imx-wm8962 instead of WM8962. So please use ASoC: fsl: imx-wm8962: or at least ASoC: imx-wm8962: The change itself looks fine though. Thanks Nic

Re: [PATCH] ASoC: WM8962: Let codec driver enable/disable its MCLK

Hi, Could you please revise the subject a bit? I forgot what's the original one I submitted (internally) years ago. But the patch is for imx-wm8962 instead of WM8962. So please use ASoC: fsl: imx-wm8962: or at least ASoC: imx-wm8962: The change itself looks fine though. Thanks Nic

Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID

On Thu, Mar 23, 2017 at 5:58 PM, Alexander Duyck wrote: > On Thu, Mar 23, 2017 at 3:43 PM, Andy Lutomirski wrote: >> On Thu, Mar 23, 2017 at 2:38 PM, Alexander Duyck >> wrote: >>> From: Sridhar Samudrala

Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID

On Thu, Mar 23, 2017 at 5:58 PM, Alexander Duyck wrote: > On Thu, Mar 23, 2017 at 3:43 PM, Andy Lutomirski wrote: >> On Thu, Mar 23, 2017 at 2:38 PM, Alexander Duyck >> wrote: >>> From: Sridhar Samudrala >>> >>> This socket option returns the NAPI ID associated with the queue on which >>> the

Re: [RFC][PATCH 0/4] printk: introduce printing kernel thread

On (03/24/17 10:59), Sergey Senozhatsky wrote: [..] > and we can jump between rescue-normal printk modes, so this should > also return back the throttling of tasks which printk() a lot (item > (2) in patch set cover letter) that we used to have. ok, I obviously lied here "this should also return

Re: [RFC][PATCH 0/4] printk: introduce printing kernel thread

On (03/24/17 10:59), Sergey Senozhatsky wrote: [..] > and we can jump between rescue-normal printk modes, so this should > also return back the throttling of tasks which printk() a lot (item > (2) in patch set cover letter) that we used to have. ok, I obviously lied here "this should also return

Re: [PATCH v2] Documentation: Input: Add uinput documentation

as usual, reading through these things multiple times means one spots a couple of different things. sorry about that. On Fri, Mar 24, 2017 at 12:34:59AM -0300, Marcos Paulo de Souza wrote: > Signed-off-by: Marcos Paulo de Souza > --- > Documentation/input/uinput.rst

Re: [PATCH v2] Documentation: Input: Add uinput documentation

as usual, reading through these things multiple times means one spots a couple of different things. sorry about that. On Fri, Mar 24, 2017 at 12:34:59AM -0300, Marcos Paulo de Souza wrote: > Signed-off-by: Marcos Paulo de Souza > --- > Documentation/input/uinput.rst | 196 >

[PATCH] drivers/staging/wilc1000: Fixing dev_err and removing dev_dbg calls for tracing

dev_err: replacing function name with '%s' and __func__ dev_dbg: Removing calls which are used for tracing a function. Signed-off-by: Pushkar Jambhlekar --- drivers/staging/wilc1000/wilc_sdio.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH] drivers/staging/wilc1000: Fixing dev_err and removing dev_dbg calls for tracing

dev_err: replacing function name with '%s' and __func__ dev_dbg: Removing calls which are used for tracing a function. Signed-off-by: Pushkar Jambhlekar --- drivers/staging/wilc1000/wilc_sdio.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, 2017-03-23 at 21:27 -0700, Eric Dumazet wrote: > If you believe min/max values should be added to the sysctls, because we > do not trust root anymore, please send patches only addressing that. extern unsigned int sysctl_net_busy_read; extern unsigned int sysctl_net_busy_poll; ...

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, 2017-03-23 at 21:27 -0700, Eric Dumazet wrote: > If you believe min/max values should be added to the sysctls, because we > do not trust root anymore, please send patches only addressing that. extern unsigned int sysctl_net_busy_read; extern unsigned int sysctl_net_busy_poll; ...

Re: [PATCH v3] extcon: intel-cht-wc: Add Intel Cherry Trail Whiskey Cove PMIC extcon driver

Hi, On 2017년 03월 24일 01:01, Hans de Goede wrote: > Add a driver for charger detection / control on the Intel Cherrytrail > Whiskey Cove PMIC. > > Signed-off-by: Hans de Goede > --- > Changes in v2: > -Improve wait for charger detection loop, use jiffies to get an accurate

Re: [PATCH v3] extcon: intel-cht-wc: Add Intel Cherry Trail Whiskey Cove PMIC extcon driver

Hi, On 2017년 03월 24일 01:01, Hans de Goede wrote: > Add a driver for charger detection / control on the Intel Cherrytrail > Whiskey Cove PMIC. > > Signed-off-by: Hans de Goede > --- > Changes in v2: > -Improve wait for charger detection loop, use jiffies to get an accurate > timeout > -Sort

Re: [PATCH v1 RESEND 1/2] x86/mm/KASLR: EFI region is mistakenly included into KASLR VA space for randomization

On 03/24/17 at 10:29am, Dave Young wrote: > Hi, Baoquan > > On 03/23/17 at 11:27am, Baoquan He wrote: > > Currently KASLR is enabled on three regions: the direct mapping of physical > > memory, vamlloc and vmemmap. However EFI region is also mistakenly included > > for VA space randomization

Re: [PATCH v1 RESEND 1/2] x86/mm/KASLR: EFI region is mistakenly included into KASLR VA space for randomization

On 03/24/17 at 10:29am, Dave Young wrote: > Hi, Baoquan > > On 03/23/17 at 11:27am, Baoquan He wrote: > > Currently KASLR is enabled on three regions: the direct mapping of physical > > memory, vamlloc and vmemmap. However EFI region is also mistakenly included > > for VA space randomization

Re: [PATCH net] net: neigh: guard against NULL solicit() method

From: Eric Dumazet Date: Thu, 23 Mar 2017 12:39:21 -0700 > From: Eric Dumazet > > Dmitry posted a nice reproducer of a bug triggering in neigh_probe() > when dereferencing a NULL neigh->ops->solicit method. > > This can happen for

Re: [PATCH net] net: neigh: guard against NULL solicit() method

From: Eric Dumazet Date: Thu, 23 Mar 2017 12:39:21 -0700 > From: Eric Dumazet > > Dmitry posted a nice reproducer of a bug triggering in neigh_probe() > when dereferencing a NULL neigh->ops->solicit method. > > This can happen for arp_direct_ops/ndisc_direct_ops and similar, > which can be

Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure

On 03/23/2017 07:41 PM, Huang, Ying wrote: David Rientjes writes: On Mon, 20 Mar 2017, Huang, Ying wrote: From: Huang Ying Now vzalloc() is used in swap code to allocate various data structures, such as swap cache, swap slots cache, cluster info,

Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure

On 03/23/2017 07:41 PM, Huang, Ying wrote: David Rientjes writes: On Mon, 20 Mar 2017, Huang, Ying wrote: From: Huang Ying Now vzalloc() is used in swap code to allocate various data structures, such as swap cache, swap slots cache, cluster info, etc. Because the size may be too large on

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, 2017-03-23 at 20:42 -0700, Alexander Duyck wrote: > On Thu, Mar 23, 2017 at 6:24 PM, Eric Dumazet wrote: > > On Thu, 2017-03-23 at 14:37 -0700, Alexander Duyck wrote: > >> From: Alexander Duyck > >> > > > >> The last bit I changed is

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, 2017-03-23 at 20:42 -0700, Alexander Duyck wrote: > On Thu, Mar 23, 2017 at 6:24 PM, Eric Dumazet wrote: > > On Thu, 2017-03-23 at 14:37 -0700, Alexander Duyck wrote: > >> From: Alexander Duyck > >> > > > >> The last bit I changed is to move from using a shift by 10 to just using > >>

Quote Request.

I WOULD LIKE TO BE FURNISHED WITH DETAILED INFORMATION ON AVAILABILITY,PRICES AND METHOD OF PAYMENT OF THE ITEM BELOW GRUNDF0S WATER PUMP GRUNDF0S 10SQ07-240 PART NUMBER 96160142 GRUNDF0S 10SQ10-290 PART NUMBER 96160143 GRUNDF0S SQ Flex 11 SQF -2 PART NUMBER 95027335 SOLAR MATERIAL MORNING

Quote Request.

I WOULD LIKE TO BE FURNISHED WITH DETAILED INFORMATION ON AVAILABILITY,PRICES AND METHOD OF PAYMENT OF THE ITEM BELOW GRUNDF0S WATER PUMP GRUNDF0S 10SQ07-240 PART NUMBER 96160142 GRUNDF0S 10SQ10-290 PART NUMBER 96160143 GRUNDF0S SQ Flex 11 SQF -2 PART NUMBER 95027335 SOLAR MATERIAL MORNING

Re: [PATCH v4 1/2] Documentation: dt-bindings: Document bindings for Aspeed ADC

On Fri, Mar 24, 2017 at 5:11 AM, Rick Altherr wrote: > Signed-off-by: Rick Altherr > --- > > Changes in v4: None > Changes in v3: > - Consistently write hex contstants with lowercase letters > - Drop model numbers from description as same IP is used in

Re: [PATCH v4 1/2] Documentation: dt-bindings: Document bindings for Aspeed ADC

On Fri, Mar 24, 2017 at 5:11 AM, Rick Altherr wrote: > Signed-off-by: Rick Altherr > --- > > Changes in v4: None > Changes in v3: > - Consistently write hex contstants with lowercase letters > - Drop model numbers from description as same IP is used in every generation > > Changes in v2: > -

Re: [PATCH v4 2/2] iio: Aspeed ADC

On Fri, Mar 24, 2017 at 5:11 AM, Rick Altherr wrote: > Aspeed BMC SoCs include a 16 channel, 10-bit ADC. Low and high threshold > interrupts are supported by the hardware but are not currently implemented. > > Signed-off-by: Rick Altherr I gave it

[PATCH] mm/hugetlb: Don't call region_abort if region_chg fails

Changes to hugetlbfs reservation maps is a two step process. The first step is a call to region_chg to determine what needs to be changed, and prepare that change. This should be followed by a call to call to region_add to commit the change, or region_abort to abort the change. The error path

Re: [PATCH v4 2/2] iio: Aspeed ADC

On Fri, Mar 24, 2017 at 5:11 AM, Rick Altherr wrote: > Aspeed BMC SoCs include a 16 channel, 10-bit ADC. Low and high threshold > interrupts are supported by the hardware but are not currently implemented. > > Signed-off-by: Rick Altherr I gave it another test with the hwmon bridge on my

[PATCH] mm/hugetlb: Don't call region_abort if region_chg fails

Changes to hugetlbfs reservation maps is a two step process. The first step is a call to region_chg to determine what needs to be changed, and prepare that change. This should be followed by a call to call to region_add to commit the change, or region_abort to abort the change. The error path

Re: [BUG nohz]: wrong user and system time accounting

On Fri, 24 Mar 2017 09:52:11 +0800 Wanpeng Li wrote: > 2017-03-24 4:55 GMT+08:00 Luiz Capitulino : > > > > When there are two or more tasks executing in user-space and > > taking 100% of a nohz_full CPU, top reports 70% system time > > and 30% user

Re: [BUG nohz]: wrong user and system time accounting

On Fri, 24 Mar 2017 09:52:11 +0800 Wanpeng Li wrote: > 2017-03-24 4:55 GMT+08:00 Luiz Capitulino : > > > > When there are two or more tasks executing in user-space and > > taking 100% of a nohz_full CPU, top reports 70% system time > > and 30% user time utilization. Sometimes I'm even able to

Re: [PATCH 0/3] minitty: a minimal TTY layer alternative for embedded systems

Hi Nicolas, On Thu, Mar 23, 2017 at 05:03:01PM -0400, Nicolas Pitre wrote: > Here's some numbers using a minimal ARM config. > > When CONFIG_TTY=y, the following files are linked into the kernel: > >textdata bss dec hex filename >8796 128 0892422dc

Re: [PATCH 0/3] minitty: a minimal TTY layer alternative for embedded systems

Hi Nicolas, On Thu, Mar 23, 2017 at 05:03:01PM -0400, Nicolas Pitre wrote: > Here's some numbers using a minimal ARM config. > > When CONFIG_TTY=y, the following files are linked into the kernel: > >textdata bss dec hex filename >8796 128 0892422dc

Re: [PATCH 3/7] iommu/iova: insert start_pfn boundary of dma32

On 2017/3/23 21:01, Robin Murphy wrote: > On 22/03/17 06:27, Zhen Lei wrote: >> Reserve the first granule size memory(start at start_pfn) as boundary >> iova, to make sure that iovad->cached32_node can not be NULL in future. >> Meanwhile, changed the assignment of iovad->cached32_node from

Re: [PATCH 3/7] iommu/iova: insert start_pfn boundary of dma32

On 2017/3/23 21:01, Robin Murphy wrote: > On 22/03/17 06:27, Zhen Lei wrote: >> Reserve the first granule size memory(start at start_pfn) as boundary >> iova, to make sure that iovad->cached32_node can not be NULL in future. >> Meanwhile, changed the assignment of iovad->cached32_node from

Re: [linux-sunxi] [PATCH v4 7/8] ARM: sun8i: h2+: enable USB OTG for Orange Pi Zero board

On Mon, Mar 20, 2017 at 12:31 AM, Icenowy Zheng wrote: > Orange Pi Zero board features a USB OTG port, which has a ID pin, and > can be used to power up the board. However, even if the board is powered > via +5V pin in GPIO/expansion headers, the VBUS in the OTG port cannot > be

Re: [linux-sunxi] [PATCH v4 7/8] ARM: sun8i: h2+: enable USB OTG for Orange Pi Zero board

On Mon, Mar 20, 2017 at 12:31 AM, Icenowy Zheng wrote: > Orange Pi Zero board features a USB OTG port, which has a ID pin, and > can be used to power up the board. However, even if the board is powered > via +5V pin in GPIO/expansion headers, the VBUS in the OTG port cannot > be powered up, thus

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, Mar 23, 2017 at 6:24 PM, Eric Dumazet wrote: > On Thu, 2017-03-23 at 14:37 -0700, Alexander Duyck wrote: >> From: Alexander Duyck >> > >> The last bit I changed is to move from using a shift by 10 to just using >> NSEC_PER_USEC and

Re: [net-next PATCH v2 5/8] net: Track start of busy loop instead of when it should end

On Thu, Mar 23, 2017 at 6:24 PM, Eric Dumazet wrote: > On Thu, 2017-03-23 at 14:37 -0700, Alexander Duyck wrote: >> From: Alexander Duyck >> > >> The last bit I changed is to move from using a shift by 10 to just using >> NSEC_PER_USEC and using multiplication for any run time calculations and

Re: [PATCH] drm/i915/kvmgt: avoid dereferencing a potentially null info pointer

On 2017.03.23 14:43:44 +0100, Frans Klaver wrote: > On Thu, Mar 23, 2017 at 1:22 PM, Colin King wrote: > > From: Colin Ian King > > > > info is being checked to see if it is a null pointer, however, vpgu is > > dereferencing info before this

Re: [PATCH] drm/i915/kvmgt: avoid dereferencing a potentially null info pointer

On 2017.03.23 14:43:44 +0100, Frans Klaver wrote: > On Thu, Mar 23, 2017 at 1:22 PM, Colin King wrote: > > From: Colin Ian King > > > > info is being checked to see if it is a null pointer, however, vpgu is > > dereferencing info before this check, leading to a potential null > > pointer

[PATCH v2] Documentation: Input: Add uinput documentation

Signed-off-by: Marcos Paulo de Souza --- Documentation/input/uinput.rst | 196 + 1 file changed, 196 insertions(+) create mode 100644 Documentation/input/uinput.rst diff --git a/Documentation/input/uinput.rst

[PATCH v2] Documentation: Input: Add uinput documentation

Signed-off-by: Marcos Paulo de Souza --- Documentation/input/uinput.rst | 196 + 1 file changed, 196 insertions(+) create mode 100644 Documentation/input/uinput.rst diff --git a/Documentation/input/uinput.rst b/Documentation/input/uinput.rst new file

Re: [PATCH v1 RESEND 1/2] x86/mm/KASLR: EFI region is mistakenly included into KASLR VA space for randomization

This should also cc linux-efi On 03/24/17 at 10:29am, Dave Young wrote: > Hi, Baoquan > > On 03/23/17 at 11:27am, Baoquan He wrote: > > Currently KASLR is enabled on three regions: the direct mapping of physical > > memory, vamlloc and vmemmap. However EFI region is also mistakenly included > >

Re: [PATCH v1 RESEND 1/2] x86/mm/KASLR: EFI region is mistakenly included into KASLR VA space for randomization

This should also cc linux-efi On 03/24/17 at 10:29am, Dave Young wrote: > Hi, Baoquan > > On 03/23/17 at 11:27am, Baoquan He wrote: > > Currently KASLR is enabled on three regions: the direct mapping of physical > > memory, vamlloc and vmemmap. However EFI region is also mistakenly included > >

linux-next: manual merge of the char-misc tree with the tpmdd tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/char/tpm/tpm-chip.c between commits: 67b67480db8b ("tpm: infrastructure for TPM spaces") b8e3586e8536 ("tpm: expose spaces via a device link /dev/tpmrm") from the tpmdd tree and commit: 8dbbf5825181

linux-next: manual merge of the char-misc tree with the tpmdd tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/char/tpm/tpm-chip.c between commits: 67b67480db8b ("tpm: infrastructure for TPM spaces") b8e3586e8536 ("tpm: expose spaces via a device link /dev/tpmrm") from the tpmdd tree and commit: 8dbbf5825181

Re: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree

On Friday 24 March 2017 02:22 AM, Tony Lindgren wrote: > * Keerthy [170321 20:45]: >> >> >> On Thursday 09 March 2017 01:35 PM, Keerthy wrote: >>> Currently the slope and offset values for calculating the >>> hot spot temperature of a particular thermal zone is part >>> of

Re: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree

On Friday 24 March 2017 02:22 AM, Tony Lindgren wrote: > * Keerthy [170321 20:45]: >> >> >> On Thursday 09 March 2017 01:35 PM, Keerthy wrote: >>> Currently the slope and offset values for calculating the >>> hot spot temperature of a particular thermal zone is part >>> of driver data. Pass

Re: [RESEND PATCH v2 26/53] mtd: nand: denali: support 1024 byte ECC step size

Hi Boris, 2017-03-23 17:39 GMT+09:00 Boris Brezillon : > On Thu, 23 Mar 2017 15:53:14 +0900 > Masahiro Yamada wrote: > >> Hi Boris, >> >> 2017-03-23 6:32 GMT+09:00 Boris Brezillon >> : >> >

Re: [RESEND PATCH v2 26/53] mtd: nand: denali: support 1024 byte ECC step size

Hi Boris, 2017-03-23 17:39 GMT+09:00 Boris Brezillon : > On Thu, 23 Mar 2017 15:53:14 +0900 > Masahiro Yamada wrote: > >> Hi Boris, >> >> 2017-03-23 6:32 GMT+09:00 Boris Brezillon >> : >> > On Thu, 23 Mar 2017 05:07:25 +0900 >> > Masahiro Yamada wrote: >> > >> >> This driver was originally

Re: [BUG?] perf: dwarf unwind doesn't work correctly on aarch64

On Thu, 23 Feb 2017 16:50:18 +0900 Masami Hiramatsu wrote: [sorry for the delay, I just saw this] > perf record -g dwarf (and perf report) doesn't show correct callchain > on aarch64. Here is how to reproduce it. ... > # Samples: 6K of event 'cpu-clock:u' > # Event count

Re: [BUG?] perf: dwarf unwind doesn't work correctly on aarch64

On Thu, 23 Feb 2017 16:50:18 +0900 Masami Hiramatsu wrote: [sorry for the delay, I just saw this] > perf record -g dwarf (and perf report) doesn't show correct callchain > on aarch64. Here is how to reproduce it. ... > # Samples: 6K of event 'cpu-clock:u' > # Event count (approx.): 162375 >

Re: [linux-sunxi] [PATCH v4 3/8] phy: sun4i-usb: add PHYCTL offset for H3 SoC

On Mon, Mar 20, 2017 at 12:19 AM, Icenowy Zheng wrote: > The config structure of H3 in phy-sun4i-usb driver have the PHYCTL > register offset missing. > > Add it. Because it's a SoC after A33, its PHYCTL offset should be 0x10. You are implying that all SoCs after A33 have

Re: [linux-sunxi] [PATCH v4 3/8] phy: sun4i-usb: add PHYCTL offset for H3 SoC

On Mon, Mar 20, 2017 at 12:19 AM, Icenowy Zheng wrote: > The config structure of H3 in phy-sun4i-usb driver have the PHYCTL > register offset missing. > > Add it. Because it's a SoC after A33, its PHYCTL offset should be 0x10. You are implying that all SoCs after A33 have PHYCTL at 0x10. This

Re: lib, fs, cgroup: WARNING in percpu_ref_kill_and_confirm

On 2017/3/23 22:04, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in percpu_ref_kill_and_confirm: > https://gist.githubusercontent.com/dvyukov/bcfcef3d6b24b9fd841b88ee20c14d4b/raw/a54aeeb09ad1e0659b0ed87ef5efc4480ab2536f/gistfile1.txt > The bug can be triggered

Re: lib, fs, cgroup: WARNING in percpu_ref_kill_and_confirm

On 2017/3/23 22:04, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in percpu_ref_kill_and_confirm: > https://gist.githubusercontent.com/dvyukov/bcfcef3d6b24b9fd841b88ee20c14d4b/raw/a54aeeb09ad1e0659b0ed87ef5efc4480ab2536f/gistfile1.txt > The bug can be triggered

Re: [linux-sunxi] [PATCH v4 2/8] phy: sun4i-usb: change PHYCTL register clearing code

On Mon, Mar 20, 2017 at 12:19 AM, Icenowy Zheng wrote: > It seems that all SoCs after A33 (including A33) need the PHYCTL > register to be cleared before writing to it. These SoCs all have another > feature: PHYCTL register is at 0x10, not 0x04. As mentioned in the other patch,

Re: [linux-sunxi] [PATCH v4 2/8] phy: sun4i-usb: change PHYCTL register clearing code

On Mon, Mar 20, 2017 at 12:19 AM, Icenowy Zheng wrote: > It seems that all SoCs after A33 (including A33) need the PHYCTL > register to be cleared before writing to it. These SoCs all have another > feature: PHYCTL register is at 0x10, not 0x04. As mentioned in the other patch, the basis for

  1   2   3   4   5   6   7   8   9   10   >