Re: [PATCH 06/14] perf tools: show NMI overhead

> how about we display the overhead information same way the main perf output: > > CPUNMI NMI timeMTX MTX time SB SB time > ... . . .. > 6 27 111379 0 0 57 90045 > > > would be just matter of

Re: [PATCH 06/14] perf tools: show NMI overhead

> how about we display the overhead information same way the main perf output: > > CPUNMI NMI timeMTX MTX time SB SB time > ... . . .. > 6 27 111379 0 0 57 90045 > > > would be just matter of

Getting at gpio- and pinctrl-devices as a consumer

On 2016-11-24 20:52, Wolfram Sang wrote: >> Yes, I never liked that include, but I don't know how to get >> from struct gpio_desc * to the relevant struct device * >> without it... > > Looks to me like we should ask the GPIO maintainers if they are willing > to export this value? I am probably

Getting at gpio- and pinctrl-devices as a consumer

On 2016-11-24 20:52, Wolfram Sang wrote: >> Yes, I never liked that include, but I don't know how to get >> from struct gpio_desc * to the relevant struct device * >> without it... > > Looks to me like we should ask the GPIO maintainers if they are willing > to export this value? I am probably

Re: [PATCH 2/5] mm: migrate: Change migrate_mode to support combination migration modes.

On 23/11/16 03:25, Zi Yan wrote: > From: Zi Yan > > From: Zi Yan > > No functionality is changed. I think you'd want to say that the modes are no longer exclusive. We can use them as flags in combination? Balbir Singh.

Re: [PATCH 2/5] mm: migrate: Change migrate_mode to support combination migration modes.

On 23/11/16 03:25, Zi Yan wrote: > From: Zi Yan > > From: Zi Yan > > No functionality is changed. I think you'd want to say that the modes are no longer exclusive. We can use them as flags in combination? Balbir Singh.

Re: [V4] powerpc: Implement {cmp}xchg for u8 and u16

On Wed, 2016-04-27 at 09:16:45 UTC, xinhui wrote: > From: Pan Xinhui > > Implement xchg{u8,u16}{local,relaxed}, and > cmpxchg{u8,u16}{,local,acquire,relaxed}. > > It works on all ppc. > > remove volatile of first parameter in __cmpxchg_local and __cmpxchg > >

Re: [PATCH -tip v3 3/9] selftests: ftrace: Add --quiet option not to show error logs on screen

On Tue, 22 Nov 2016 14:44:59 -0500 Steven Rostedt wrote: > On Wed, 16 Nov 2016 17:13:17 +0900 > Masami Hiramatsu wrote: > > > Since the verbose error logs scrolls out previous test results > > --quiet option suppress to show such message. > > I wonder

Re: [V4] powerpc: Implement {cmp}xchg for u8 and u16

On Wed, 2016-04-27 at 09:16:45 UTC, xinhui wrote: > From: Pan Xinhui > > Implement xchg{u8,u16}{local,relaxed}, and > cmpxchg{u8,u16}{,local,acquire,relaxed}. > > It works on all ppc. > > remove volatile of first parameter in __cmpxchg_local and __cmpxchg > > Suggested-by: Peter Zijlstra

Re: [PATCH -tip v3 3/9] selftests: ftrace: Add --quiet option not to show error logs on screen

On Tue, 22 Nov 2016 14:44:59 -0500 Steven Rostedt wrote: > On Wed, 16 Nov 2016 17:13:17 +0900 > Masami Hiramatsu wrote: > > > Since the verbose error logs scrolls out previous test results > > --quiet option suppress to show such message. > > I wonder if -q should be default, and -v be what

Re: [v2, 1/2] powerpc: initial stack protector (-fstack-protector) support

On Tue, 2016-11-22 at 10:49:30 UTC, Christophe Leroy wrote: > Partialy copied from commit c743f38013aef ("ARM: initial stack protector > (-fstack-protector) support") > > This is the very basic stuff without the changing canary upon > task switch yet. Just the Kconfig option and a constant

Re: [v2, 1/2] powerpc: initial stack protector (-fstack-protector) support

On Tue, 2016-11-22 at 10:49:30 UTC, Christophe Leroy wrote: > Partialy copied from commit c743f38013aef ("ARM: initial stack protector > (-fstack-protector) support") > > This is the very basic stuff without the changing canary upon > task switch yet. Just the Kconfig option and a constant

Re: [PATCH 0/5] Parallel hugepage migration optimization

On 23/11/16 03:25, Zi Yan wrote: > From: Zi Yan > > Hi all, > > This patchset boosts the hugepage migration throughput and helps THP migration > which is added by Naoya's patches: https://lwn.net/Articles/705879/. > > Motivation > === > >

Re: [PATCH 0/5] Parallel hugepage migration optimization

On 23/11/16 03:25, Zi Yan wrote: > From: Zi Yan > > Hi all, > > This patchset boosts the hugepage migration throughput and helps THP migration > which is added by Naoya's patches: https://lwn.net/Articles/705879/. > > Motivation > === > > In x86, 4KB page

Re: [PATCH 1/5] mm: migrate: Add mode parameter to support additional page copy routines.

On 23/11/16 03:25, Zi Yan wrote: > From: Zi Yan > > From: Zi Yan > > migrate_page_copy() and copy_huge_page() are affected. > > Signed-off-by: Zi Yan > Signed-off-by: Zi Yan > --- > fs/aio.c|

Re: [PATCH 1/5] mm: migrate: Add mode parameter to support additional page copy routines.

On 23/11/16 03:25, Zi Yan wrote: > From: Zi Yan > > From: Zi Yan > > migrate_page_copy() and copy_huge_page() are affected. > > Signed-off-by: Zi Yan > Signed-off-by: Zi Yan > --- > fs/aio.c| 2 +- > fs/hugetlbfs/inode.c| 2 +- > fs/ubifs/file.c | 2 +- >

[mdadm PATCH] Add failfast support.

Allow per-device "failfast" flag to be set when creating an array or adding devices to an array. When re-adding a device which had the failfast flag, it can be removed using --nofailfast. failfast status is printed in --detail and --examine output. Signed-off-by: NeilBrown ---

[mdadm PATCH] Add failfast support.

Allow per-device "failfast" flag to be set when creating an array or adding devices to an array. When re-adding a device which had the failfast flag, it can be removed using --nofailfast. failfast status is printed in --detail and --examine output. Signed-off-by: NeilBrown --- Hi Jes, this

Multiple problems with the Linux kernel on an AMD desktop

Dear developers, I have been having problems that are starting to accumulate on my main Desktop and I decided to ask here for help, since I perceive that the majority (not all, of course) of developers are likely to use recent, Intel-based systems for their x86-64 work. My desktop has an AMD

Multiple problems with the Linux kernel on an AMD desktop

Dear developers, I have been having problems that are starting to accumulate on my main Desktop and I decided to ask here for help, since I perceive that the majority (not all, of course) of developers are likely to use recent, Intel-based systems for their x86-64 work. My desktop has an AMD

Re: [PATCH 06/14] perf tools: show NMI overhead

On Fri, Nov 25, 2016 at 08:20:13AM +0900, Namhyung Kim wrote: > Hi, > > On Thu, Nov 24, 2016 at 04:27:21PM +0100, Jiri Olsa wrote: > > On Thu, Nov 24, 2016 at 01:37:04PM +, Liang, Kan wrote: > > > > > > > > > > > > > > On Wed, Nov 23, 2016 at 04:44:44AM -0500, kan.li...@intel.com wrote: >

Re: [PATCH 06/14] perf tools: show NMI overhead

On Fri, Nov 25, 2016 at 08:20:13AM +0900, Namhyung Kim wrote: > Hi, > > On Thu, Nov 24, 2016 at 04:27:21PM +0100, Jiri Olsa wrote: > > On Thu, Nov 24, 2016 at 01:37:04PM +, Liang, Kan wrote: > > > > > > > > > > > > > > On Wed, Nov 23, 2016 at 04:44:44AM -0500, kan.li...@intel.com wrote: >

Re: linux-next: build failure after merge of the akpm-current tree

Hi Thiago, On Thu, 24 Nov 2016 13:02:39 -0200 Thiago Jung Bauermann wrote: > > Am Donnerstag, 24. November 2016, 16:01:51 BRST schrieb Stephen Rothwell: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build (powerpc > >

Re: linux-next: build failure after merge of the akpm-current tree

Hi Thiago, On Thu, 24 Nov 2016 13:02:39 -0200 Thiago Jung Bauermann wrote: > > Am Donnerstag, 24. November 2016, 16:01:51 BRST schrieb Stephen Rothwell: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > >

Re: [PATCH 0/2] KEYS: Fixes

James Morris <jmor...@namei.org> wrote: > $ git pull > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > keys-fixes-20161124-3 > fatal: Couldn't find remote ref keys-fixes-20161124-3 Ummm... Weird. I can see the tag through the web interfa

Re: [PATCH 0/2] KEYS: Fixes

James Morris wrote: > $ git pull > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > keys-fixes-20161124-3 > fatal: Couldn't find remote ref keys-fixes-20161124-3 Ummm... Weird. I can see the tag through the web interface: http://git.kernel.or

[RFC] pinctrl: imx: use radix trees for groups and functions

This change is inspired from the pinctrl-single architecture. The problem with current implementation is that it isn't possible to add/remove functions and/or groups dynamically. The radix tree offers an easy way to do so. The intent is to offer a follow-up patch later that will enable the use of

[RFC] pinctrl: imx: use radix trees for groups and functions

This change is inspired from the pinctrl-single architecture. The problem with current implementation is that it isn't possible to add/remove functions and/or groups dynamically. The radix tree offers an easy way to do so. The intent is to offer a follow-up patch later that will enable the use of

Re: [PATCH 1/6] PM / devfreq: Fix the checkpatch warnings

On 2016년 11월 24일 19:52, Joe Perches wrote: > On Thu, 2016-11-24 at 19:46 +0900, Chanwoo Choi wrote: >> On 2016년 11월 24일 19:20, Joe Perches wrote: >>> On Thu, 2016-11-24 at 14:01 +0900, Chanwoo Choi wrote: This patch just fixes the checkpatch warnings. >>> >>> unrelated trivia: >>> diff

Re: [PATCH 1/6] PM / devfreq: Fix the checkpatch warnings

On 2016년 11월 24일 19:52, Joe Perches wrote: > On Thu, 2016-11-24 at 19:46 +0900, Chanwoo Choi wrote: >> On 2016년 11월 24일 19:20, Joe Perches wrote: >>> On Thu, 2016-11-24 at 14:01 +0900, Chanwoo Choi wrote: This patch just fixes the checkpatch warnings. >>> >>> unrelated trivia: >>> diff

Re: Getting at gpio- and pinctrl-devices as a consumer

On Thu, Nov 24, 2016 at 10:35 PM, Peter Rosin wrote: > The background is that the gpio- and pinctrl-based i2c-mux drivers > need to know if the device that is used to control the mux of the > i2c-bus is also sitting on that very same i2c-bus. If it is, the > locking has to be

Re: Getting at gpio- and pinctrl-devices as a consumer

On Thu, Nov 24, 2016 at 10:35 PM, Peter Rosin wrote: > The background is that the gpio- and pinctrl-based i2c-mux drivers > need to know if the device that is used to control the mux of the > i2c-bus is also sitting on that very same i2c-bus. If it is, the > locking has to be different and a bit

Re: [PATCH 0/2] KEYS: Fixes

On Thu, 24 Nov 2016, David Howells wrote: > James Morris <jmor...@namei.org> wrote: > > > $ git pull > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > > keys-fixes-20161124 > > fatal: Couldn't find remote ref keys-fixes-20161124 >

Re: [PATCH 0/2] KEYS: Fixes

On Thu, 24 Nov 2016, David Howells wrote: > James Morris wrote: > > > $ git pull > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > > keys-fixes-20161124 > > fatal: Couldn't find remote ref keys-fixes-20161124 > > I've produced tw

Re: [PATCH 02/14] perf/x86: output NMI overhead

On Thu, Nov 24, 2016 at 07:40:21PM +, Liang, Kan wrote: > > > > > @@ -1492,8 +1507,10 @@ perf_event_nmi_handler(unsigned int cmd, > > struct pt_regs *regs) > > > start_clock = sched_clock(); > > > ret = x86_pmu.handle_irq(regs); > > > finish_clock = sched_clock(); > > > + clock =

Re: [PATCH 02/14] perf/x86: output NMI overhead

On Thu, Nov 24, 2016 at 07:40:21PM +, Liang, Kan wrote: > > > > > @@ -1492,8 +1507,10 @@ perf_event_nmi_handler(unsigned int cmd, > > struct pt_regs *regs) > > > start_clock = sched_clock(); > > > ret = x86_pmu.handle_irq(regs); > > > finish_clock = sched_clock(); > > > + clock =

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

Mostly it seems we are in understanding here, looking forward to the patches... On Thu, Nov 24, 2016 at 5:32 PM, Thierry Reding wrote: > On Thu, Nov 24, 2016 at 04:08:08PM +0100, Linus Walleij wrote: >> I don't understand. Userspace should have no concern about the >>

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

Mostly it seems we are in understanding here, looking forward to the patches... On Thu, Nov 24, 2016 at 5:32 PM, Thierry Reding wrote: > On Thu, Nov 24, 2016 at 04:08:08PM +0100, Linus Walleij wrote: >> I don't understand. Userspace should have no concern about the >> numberspace. Lines can be

[PATCH 2/3] pinctrl: sx150x: sort chips by part number

Signed-off-by: Peter Rosin --- .../devicetree/bindings/pinctrl/pinctrl-sx150x.txt | 6 +- drivers/pinctrl/pinctrl-sx150x.c | 142 ++--- 2 files changed, 74 insertions(+), 74 deletions(-) diff --git

[PATCH 2/3] pinctrl: sx150x: sort chips by part number

Signed-off-by: Peter Rosin --- .../devicetree/bindings/pinctrl/pinctrl-sx150x.txt | 6 +- drivers/pinctrl/pinctrl-sx150x.c | 142 ++--- 2 files changed, 74 insertions(+), 74 deletions(-) diff --git

Re: [PATCH 06/14] perf tools: show NMI overhead

Hi, On Thu, Nov 24, 2016 at 04:27:21PM +0100, Jiri Olsa wrote: > On Thu, Nov 24, 2016 at 01:37:04PM +, Liang, Kan wrote: > > > > > > > > > > On Wed, Nov 23, 2016 at 04:44:44AM -0500, kan.li...@intel.com wrote: > > > > From: Kan Liang > > > > > > > > Caculate the total

[PATCH v3 0/2] perf probe: add sdt probes arguments into the uprobe cmd string

Hi Hemant, Once more thank you for your answer. Sorry for this bug: I tested the patches only on small sample binaries. Now it is tested against the systemtap-enabled libraries libc and libpthread. There were 2 problems: * The one you disclosed: in indirect addressing mode, positive offsets

[PATCH v3 2/2] perf probe: add sdt probes arguments into the uprobe cmd string

An sdt probe can be associated with arguments but they were not passed to the user probe tracing interface (uprobe_events); this patch adapts the sdt argument descriptors according to the uprobe input format. As the uprobe parser does not support scaled address mode, perf will skip arguments

Re: [PATCH 06/14] perf tools: show NMI overhead

Hi, On Thu, Nov 24, 2016 at 04:27:21PM +0100, Jiri Olsa wrote: > On Thu, Nov 24, 2016 at 01:37:04PM +, Liang, Kan wrote: > > > > > > > > > > On Wed, Nov 23, 2016 at 04:44:44AM -0500, kan.li...@intel.com wrote: > > > > From: Kan Liang > > > > > > > > Caculate the total NMI overhead on each

[PATCH v3 0/2] perf probe: add sdt probes arguments into the uprobe cmd string

Hi Hemant, Once more thank you for your answer. Sorry for this bug: I tested the patches only on small sample binaries. Now it is tested against the systemtap-enabled libraries libc and libpthread. There were 2 problems: * The one you disclosed: in indirect addressing mode, positive offsets

[PATCH v3 2/2] perf probe: add sdt probes arguments into the uprobe cmd string

An sdt probe can be associated with arguments but they were not passed to the user probe tracing interface (uprobe_events); this patch adapts the sdt argument descriptors according to the uprobe input format. As the uprobe parser does not support scaled address mode, perf will skip arguments

[PATCH v3 1/2] perf sdt: add scanning of sdt probles arguments

During a "perf buildid-cache --add" command, the section ".note.stapsdt" of the "added" binary is scanned in order to list the available SDT markers available in a binary. The parts containing the probes arguments were left unscanned. The whole section is now parsed; the probe arguments are

[PATCH v3 1/2] perf sdt: add scanning of sdt probles arguments

During a "perf buildid-cache --add" command, the section ".note.stapsdt" of the "added" binary is scanned in order to list the available SDT markers available in a binary. The parts containing the probes arguments were left unscanned. The whole section is now parsed; the probe arguments are

Re: [PATCH 0/2] KEYS: Fixes

James Morris <jmor...@namei.org> wrote: > $ git pull > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > keys-fixes-20161124 > fatal: Couldn't find remote ref keys-fixes-20161124 I've produced two further versions of this. Can you look at keys-fixes-

Re: [PATCH 0/2] KEYS: Fixes

James Morris wrote: > $ git pull > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > keys-fixes-20161124 > fatal: Couldn't find remote ref keys-fixes-20161124 I've produced two further versions of this. Can you look at keys-fixes-20161124-3 instead? David

[PATCH v2 net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

Add driver for Alacritech gigabit ethernet cards with SLIC (session-layer interface control) technology. The driver provides basic support without SLIC for the following devices: - Mojave cards (single port PCI Gigabit) both copper and fiber - Oasis cards (single and dual port PCI-x Gigabit)

[PATCH v2 net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

Add driver for Alacritech gigabit ethernet cards with SLIC (session-layer interface control) technology. The driver provides basic support without SLIC for the following devices: - Mojave cards (single port PCI Gigabit) both copper and fiber - Oasis cards (single and dual port PCI-x Gigabit)

Gigabit ethernet driver for Alacritechs SLIC devices

Hi, this is the second version of the slicoss gigabit ethernet driver (which is a rework of the driver from Alacritech which can currently be found under drivers/staging/slicoss). The driver is supposed to support Mojave, Oasis and Kalahari cards, for both copper and fiber. If this code is

[PATCH v2 net-next 2/2] MAINTAINERS: add entry for slicoss ethernet driver

Add myself as maintainer for the slicoss ethernet driver. Signed-off-by: Lino Sanfilippo --- MAINTAINERS | 5 + 1 file changed, 5 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 6781a3f..bb9af28 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -562,6 +562,11

[PATCH v2 net-next 2/2] MAINTAINERS: add entry for slicoss ethernet driver

Add myself as maintainer for the slicoss ethernet driver. Signed-off-by: Lino Sanfilippo --- MAINTAINERS | 5 + 1 file changed, 5 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 6781a3f..bb9af28 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -562,6 +562,11 @@ T: git

Gigabit ethernet driver for Alacritechs SLIC devices

Hi, this is the second version of the slicoss gigabit ethernet driver (which is a rework of the driver from Alacritech which can currently be found under drivers/staging/slicoss). The driver is supposed to support Mojave, Oasis and Kalahari cards, for both copper and fiber. If this code is

Re: [PATCH 4.4 00/31] 4.4.35-stable review

On 11/24/2016 06:55 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.35 release. There are 31 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.4 00/31] 4.4.35-stable review

On 11/24/2016 06:55 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.35 release. There are 31 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

[PATCH] MAINTAINERS: Add bug tracking system location entry type

From: Rafael J. Wysocki Following the kernel Bugzilla discussion during the Kernel Summit (https://lwn.net/Articles/705245/), add bug tracking system location entry type (B) to MAINTAINERS and populate it for several subsystems known to be using the kernel BZ actively

[PATCH] MAINTAINERS: Add bug tracking system location entry type

From: Rafael J. Wysocki Following the kernel Bugzilla discussion during the Kernel Summit (https://lwn.net/Articles/705245/), add bug tracking system location entry type (B) to MAINTAINERS and populate it for several subsystems known to be using the kernel BZ actively (and add the upstream BZ

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): > Hi Serge, > > On 11/19/2016 04:17 PM, Serge E. Hallyn wrote: > > Root in a user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): > Hi Serge, > > On 11/19/2016 04:17 PM, Serge E. Hallyn wrote: > > Root in a user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could

Re: [PATCH v2 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

Hi Hari, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

Hi Hari, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] locking-selftest: Fix output since KERN_CONT changes

Since the KERN_CONT changes the locking-selftest output is messed up, eg: | spin |wlock |rlock |mutex | wsem | rsem |

[PATCH] locking-selftest: Fix output since KERN_CONT changes

Since the KERN_CONT changes the locking-selftest output is messed up, eg: | spin |wlock |rlock |mutex | wsem | rsem |

Re: [PATCH 0/2] KEYS: Fixes

e free in X.509 error handling. > > The patches can be found here also: > > > http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes > > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git >

Re: [PATCH 0/2] KEYS: Fixes

e free in X.509 error handling. > > The patches can be found here also: > > > http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes > > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git >

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > On Thu, Nov 24, 2016 at 04:10:49PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > > > Looks like git send-email is not able to parse this address correctly > > though this is suggested format by Documentation/stable_kernel_rules.txt. > > Create wrong address If

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > On Thu, Nov 24, 2016 at 04:10:49PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > > > Looks like git send-email is not able to parse this address correctly > > though this is suggested format by Documentation/stable_kernel_rules.txt. > > Create wrong address If git parsers is used :

Re: [PATCH] stmmac ethernet: remove cut & paste code

On Thu, 2016-11-24 at 22:44 +0100, Pavel Machek wrote: > On Thu 2016-11-24 12:05:25, Joe Perches wrote: > > On Thu, 2016-11-24 at 12:05 +0100, Pavel Machek wrote: > > > Remove duplicate code from _tx routines. > > > > trivia: > > > > > diff --git

Re: [PATCH] stmmac ethernet: remove cut & paste code

On Thu, 2016-11-24 at 22:44 +0100, Pavel Machek wrote: > On Thu 2016-11-24 12:05:25, Joe Perches wrote: > > On Thu, 2016-11-24 at 12:05 +0100, Pavel Machek wrote: > > > Remove duplicate code from _tx routines. > > > > trivia: > > > > > diff --git

hey!

I just wanna be your friend if you can reply me back, Call me Monica.

hey!

I just wanna be your friend if you can reply me back, Call me Monica.

Re: [PATCH] ARM: pxa: ezx: fix a910 camera data

Hello. On 24.11.2016 17:29, Arnd Bergmann wrote: > The camera_supply_dummy_device definition is shared between a780 and a910, > but only provided when the first is enabled and fails to build for a > configuration with only a910: > > arch/arm/mach-pxa/ezx.c:1097:3: error:

Re: [PATCH] ARM: pxa: ezx: fix a910 camera data

Hello. On 24.11.2016 17:29, Arnd Bergmann wrote: > The camera_supply_dummy_device definition is shared between a780 and a910, > but only provided when the first is enabled and fails to build for a > configuration with only a910: > > arch/arm/mach-pxa/ezx.c:1097:3: error:

[PATCH] dt-bindings: document how to setup rockchip timers as clocksource

The patch describes how to setup rockchip timers in device tree so they can be used as clocksource. I'm going to implement this feature. Signed-off-by: Alexander Kochetkov --- .../bindings/timer/rockchip,rk-timer.txt | 35 +++- 1 file changed,

[PATCH] dt-bindings: document how to setup rockchip timers as clocksource

The patch describes how to setup rockchip timers in device tree so they can be used as clocksource. I'm going to implement this feature. Signed-off-by: Alexander Kochetkov --- .../bindings/timer/rockchip,rk-timer.txt | 35 +++- 1 file changed, 34 insertions(+), 1

[PATCH] staging: most: Eliminate symbolic permissions usage

Fix checkpatch warnings regarding the use of symbolic permissions. Where the MOST_CHANNEL_ATTR macro is used, convert to octal permissions over symbolic. Where _ATTR is used directly, replace with _ATTR_RW/_ATTR_WO and update the show/store function names appropriately. Signed-off-by: Jason

[PATCH] staging: most: Eliminate symbolic permissions usage

Fix checkpatch warnings regarding the use of symbolic permissions. Where the MOST_CHANNEL_ATTR macro is used, convert to octal permissions over symbolic. Where _ATTR is used directly, replace with _ATTR_RW/_ATTR_WO and update the show/store function names appropriately. Signed-off-by: Jason

[PATCH] dt-bindings: clarify compatible field usage for rockchip timers

rk3036 dtsi file already use compatible field as "rockchip,rk3036-timer", "rockchip,rk3288-timer". The patch clearly shows how that filed should be used on other chips. Signed-off-by: Alexander Kochetkov --- .../bindings/timer/rockchip,rk-timer.txt | 12

[PATCH] dt-bindings: clarify compatible field usage for rockchip timers

rk3036 dtsi file already use compatible field as "rockchip,rk3036-timer", "rockchip,rk3288-timer". The patch clearly shows how that filed should be used on other chips. Signed-off-by: Alexander Kochetkov --- .../bindings/timer/rockchip,rk-timer.txt | 12 +--- 1 file

Re: [PATCH] stmmac ethernet: remove cut & paste code

On Thu 2016-11-24 12:05:25, Joe Perches wrote: > On Thu, 2016-11-24 at 12:05 +0100, Pavel Machek wrote: > > Remove duplicate code from _tx routines. > > trivia: > > > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > > b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > [] > >

Re: [PATCH] stmmac ethernet: remove cut & paste code

On Thu 2016-11-24 12:05:25, Joe Perches wrote: > On Thu, 2016-11-24 at 12:05 +0100, Pavel Machek wrote: > > Remove duplicate code from _tx routines. > > trivia: > > > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > > b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > [] > >

[PATCH v3] i2c: i2c-mux-gpio: update mux with gpiod_set_array_value_cansleep

If the gpio controller supports it and the gpio lines are concentrated to one gpio chip, the mux controller pins will get updated simultaneously. Signed-off-by: Peter Rosin --- drivers/i2c/muxes/i2c-mux-gpio.c | 18 ++ 1 file changed, 14 insertions(+), 4

[PATCH v3] i2c: i2c-mux-gpio: update mux with gpiod_set_array_value_cansleep

If the gpio controller supports it and the gpio lines are concentrated to one gpio chip, the mux controller pins will get updated simultaneously. Signed-off-by: Peter Rosin --- drivers/i2c/muxes/i2c-mux-gpio.c | 18 ++ 1 file changed, 14 insertions(+), 4 deletions(-) Hi! v2 ->

Re: [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board

On Wed, Nov 23, 2016 at 09:23:49AM +, Andre Przywara wrote: > Hi Maxime, > > On 23/11/16 07:57, Maxime Ripard wrote: > > On Tue, Nov 22, 2016 at 12:24:20AM +0800, Icenowy Zheng wrote: > >> Orange Pi Zero is a board that came with the new Allwinner H2+ SoC. > >> > >> Add a device tree file for

Re: [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board

On Wed, Nov 23, 2016 at 09:23:49AM +, Andre Przywara wrote: > Hi Maxime, > > On 23/11/16 07:57, Maxime Ripard wrote: > > On Tue, Nov 22, 2016 at 12:24:20AM +0800, Icenowy Zheng wrote: > >> Orange Pi Zero is a board that came with the new Allwinner H2+ SoC. > >> > >> Add a device tree file for

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

> On 24 November 2016 at 21:39 Al Viro wrote: > > > On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > > data=journal mount option should disable O_DIRECT access > > (See Documentation/filesystems/ext4.txt) but open operations > > using

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

> On 24 November 2016 at 21:39 Al Viro wrote: > > > On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > > data=journal mount option should disable O_DIRECT access > > (See Documentation/filesystems/ext4.txt) but open operations > > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no

RFC: documentation of the autogroup feature [v2]

Hi Mike, I reworked the text on autogroups, and in the process learned something/have another question. Could you tell me if anything in the below needs fixing/improving, and also let me know about the FIXME? Thanks, Michael The autogroup feature Since Linux 2.6.38, the kernel

RFC: documentation of the autogroup feature [v2]

Hi Mike, I reworked the text on autogroups, and in the process learned something/have another question. Could you tell me if anything in the below needs fixing/improving, and also let me know about the FIXME? Thanks, Michael The autogroup feature Since Linux 2.6.38, the kernel

Re: [PATCH 3/3] ARM: dts: sunxi: enable SDIO Wi-Fi on Orange Pi Zero

On Wed, Nov 23, 2016 at 10:25:57PM +0800, Chen-Yu Tsai wrote: > >> _pio { > >> @@ -111,6 +148,11 @@ > >> pins = "PL10"; > >> function = "gpio_out"; > >> }; > >> + > >> + wifi_pwrseq_pin_opi0: wifi_pwrseq_pin@0 { > >> + allwinner,pins = "PL7"; > >>

Re: [PATCH 3/3] ARM: dts: sunxi: enable SDIO Wi-Fi on Orange Pi Zero

On Wed, Nov 23, 2016 at 10:25:57PM +0800, Chen-Yu Tsai wrote: > >> _pio { > >> @@ -111,6 +148,11 @@ > >> pins = "PL10"; > >> function = "gpio_out"; > >> }; > >> + > >> + wifi_pwrseq_pin_opi0: wifi_pwrseq_pin@0 { > >> + allwinner,pins = "PL7"; > >>

Re: stmmac ethernet in kernel 4.9-rc6: coalescing related pauses.

Hi! > >> I'm debugging strange delays during transmit in stmmac driver. They > >> seem to be present in 4.4 kernel (and older kernels, too). Workload is > >> burst of udp packets being sent, pause, burst of udp packets, ... ... > > 4.9-rc6 still has the delays. With the > > > > #define

Re: stmmac ethernet in kernel 4.9-rc6: coalescing related pauses.

Hi! > >> I'm debugging strange delays during transmit in stmmac driver. They > >> seem to be present in 4.4 kernel (and older kernels, too). Workload is > >> burst of udp packets being sent, pause, burst of udp packets, ... ... > > 4.9-rc6 still has the delays. With the > > > > #define

[PATCH 0/3] sx150x update - bugfix, cleanup, last 4 chips

Hi! Yet another sx150x update, only the first is critical. Cheers, Peter Peter Rosin (3): pinctrl: sx150x: use correct registers for reg_sense (sx1502 and sx1508) pinctrl: sx150x: sort chips by part number pinctrl: sx150x: add support for sx1501, sx1504, sx1505 and sx1507

[PATCH 0/3] sx150x update - bugfix, cleanup, last 4 chips

Hi! Yet another sx150x update, only the first is critical. Cheers, Peter Peter Rosin (3): pinctrl: sx150x: use correct registers for reg_sense (sx1502 and sx1508) pinctrl: sx150x: sort chips by part number pinctrl: sx150x: add support for sx1501, sx1504, sx1505 and sx1507

Re: [PATCH v5 4/5] ACPI 2.0 / AML: Improve module level execution by moving the If/Else/While execution to per-table basis

On Fri, Sep 23, 2016 at 5:26 AM, Lv Zheng wrote: > This reverts commit 00c611def8748a0a1cf1d31842e49b42dfdb3de1. It would be good to say why it is now OK to revert it. Thanks, Rafael

Re: [PATCH v5 4/5] ACPI 2.0 / AML: Improve module level execution by moving the If/Else/While execution to per-table basis

On Fri, Sep 23, 2016 at 5:26 AM, Lv Zheng wrote: > This reverts commit 00c611def8748a0a1cf1d31842e49b42dfdb3de1. It would be good to say why it is now OK to revert it. Thanks, Rafael

<    1   2   3   4   5   6   7   8   9   10   >