Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore

On Fri, 4 May 2018, Paul E. McKenney wrote: > On Fri, May 04, 2018 at 11:38:37PM -0500, Eric W. Biederman wrote: > > > (Me, I would run rcutorture scenario TREE03 for an extended time period > > > on b4abf91047cf with your patch applied. > > And with lockdep enabled, which TREE03 does not do by

Re: [PATCH 2/2] dmaengine: sprd: Add Spreadtrum DMA configuration

Hi Eric, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on slave-dma/next] [also build test WARNING on next-20180504] [cannot apply to linus/master v4.17-rc3] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url

Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore

On Fri, 4 May 2018, Paul E. McKenney wrote: > On Fri, May 04, 2018 at 11:38:37PM -0500, Eric W. Biederman wrote: > > > (Me, I would run rcutorture scenario TREE03 for an extended time period > > > on b4abf91047cf with your patch applied. > > And with lockdep enabled, which TREE03 does not do by

Re: [PATCH 2/2] dmaengine: sprd: Add Spreadtrum DMA configuration

Hi Eric, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on slave-dma/next] [also build test WARNING on next-20180504] [cannot apply to linus/master v4.17-rc3] [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] Revert "f2fs: add ovp valid_blocks check for bg gc victim to fg_gc"

Ping, On 2018/4/27 10:55, Chao Yu wrote: > Hi Jaegeuk, > > Missed this patch, or any problem in it? > > Thanks, > > On 2018/4/26 17:05, Chao Yu wrote: >> For extreme case: >> 10 section, op = 10%, no_fggc_threshold = 90% >> All section usage: 85% 85% 85% 85% 90% 90% 95% 95% 95% 95% >> >>

Re: [PATCH 2/2] Revert "f2fs: add ovp valid_blocks check for bg gc victim to fg_gc"

Ping, On 2018/4/27 10:55, Chao Yu wrote: > Hi Jaegeuk, > > Missed this patch, or any problem in it? > > Thanks, > > On 2018/4/26 17:05, Chao Yu wrote: >> For extreme case: >> 10 section, op = 10%, no_fggc_threshold = 90% >> All section usage: 85% 85% 85% 85% 90% 90% 95% 95% 95% 95% >> >>

Re: [PATCH] f2fs: fix to wait IO writeback in __revoke_inmem_pages()

Ping, On 2018/4/27 10:37, Chao Yu wrote: > On 2018/4/27 0:36, Jaegeuk Kim wrote: >> On 04/26, Chao Yu wrote: >>> On 2018/4/26 23:48, Jaegeuk Kim wrote: On 04/26, Chao Yu wrote: > Thread A Thread B > - f2fs_ioc_commit_atomic_write > - commit_inmem_pages

Re: [PATCH] f2fs: fix to wait IO writeback in __revoke_inmem_pages()

Ping, On 2018/4/27 10:37, Chao Yu wrote: > On 2018/4/27 0:36, Jaegeuk Kim wrote: >> On 04/26, Chao Yu wrote: >>> On 2018/4/26 23:48, Jaegeuk Kim wrote: On 04/26, Chao Yu wrote: > Thread A Thread B > - f2fs_ioc_commit_atomic_write > - commit_inmem_pages

Re: [PATCH 2/2] leds: Add Spreadtrum SC27xx breathing light controller driver

Hi Xiaotong, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.17-rc3 next-20180504] [cannot apply to j.anaszewski-leds/for-next] [if your patch is applied to the wrong git tree, please drop us a note to help improve

Re: [PATCH 2/2] leds: Add Spreadtrum SC27xx breathing light controller driver

Hi Xiaotong, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.17-rc3 next-20180504] [cannot apply to j.anaszewski-leds/for-next] [if your patch is applied to the wrong git tree, please drop us a note to help improve

Re: [Ksummit-discuss] bug-introducing patches

On Fri, May 04, 2018 at 07:35:42PM -0400, Theodore Y. Ts'o wrote: >On Fri, May 04, 2018 at 09:51:14PM +, Sasha Levin wrote: >> I don't have an objection to moving this to it's own tag. It will make >> my scripts somewhat simpler for sure. > >It's not a matter "moving this it's own tag", but

Re: [Ksummit-discuss] bug-introducing patches

On Fri, May 04, 2018 at 07:35:42PM -0400, Theodore Y. Ts'o wrote: >On Fri, May 04, 2018 at 09:51:14PM +, Sasha Levin wrote: >> I don't have an objection to moving this to it's own tag. It will make >> my scripts somewhat simpler for sure. > >It's not a matter "moving this it's own tag", but

Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore

On Fri, May 04, 2018 at 11:38:37PM -0500, Eric W. Biederman wrote: > "Paul E. McKenney" writes: > > > On Fri, May 04, 2018 at 03:08:40PM -0500, Eric W. Biederman wrote: > >> "Paul E. McKenney" writes: > >> > >> > On Fri, May 04, 2018 at

Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore

On Fri, May 04, 2018 at 11:38:37PM -0500, Eric W. Biederman wrote: > "Paul E. McKenney" writes: > > > On Fri, May 04, 2018 at 03:08:40PM -0500, Eric W. Biederman wrote: > >> "Paul E. McKenney" writes: > >> > >> > On Fri, May 04, 2018 at 02:03:04PM -0500, Eric W. Biederman wrote: > >> >> "Paul

Re: Suggested new user link command

Tony Wallace writes: > On 02/05/18 01:35, Bernd Petrovitsch wrote: >> Hi all! >> >> Top-quoting is evil BTW. >> >> On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: >>> Two issues here: >>> 1) Use case (which I have) >>> 2) Permissions >>> >>> 1) Use case >>> >>> I am

Re: Suggested new user link command

Tony Wallace writes: > On 02/05/18 01:35, Bernd Petrovitsch wrote: >> Hi all! >> >> Top-quoting is evil BTW. >> >> On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: >>> Two issues here: >>> 1) Use case (which I have) >>> 2) Permissions >>> >>> 1) Use case >>> >>> I am trying to build a

Re: [Ksummit-discuss] bug-introducing patches

Willy Tarreau writes: > On Fri, May 04, 2018 at 07:35:42PM -0400, Theodore Y. Ts'o wrote: >> On Fri, May 04, 2018 at 09:51:14PM +, Sasha Levin wrote: >> > I don't have an objection to moving this to it's own tag. It will make >> > my scripts somewhat simpler for sure. >> >>

Re: [Ksummit-discuss] bug-introducing patches

Willy Tarreau writes: > On Fri, May 04, 2018 at 07:35:42PM -0400, Theodore Y. Ts'o wrote: >> On Fri, May 04, 2018 at 09:51:14PM +, Sasha Levin wrote: >> > I don't have an objection to moving this to it's own tag. It will make >> > my scripts somewhat simpler for sure. >> >> It's not a

Re: [PATCH v2 net-next 1/4] umh: introduce fork_usermode_blob() helper

On Thu, May 3, 2018 at 12:36 AM, Alexei Starovoitov wrote: > Introduce helper: > int fork_usermode_blob(void *data, size_t len, struct umh_info *info); > struct umh_info { >struct file *pipe_to_umh; >struct file *pipe_from_umh; >pid_t pid; > }; > > that

Re: [PATCH v2 net-next 1/4] umh: introduce fork_usermode_blob() helper

On Thu, May 3, 2018 at 12:36 AM, Alexei Starovoitov wrote: > Introduce helper: > int fork_usermode_blob(void *data, size_t len, struct umh_info *info); > struct umh_info { >struct file *pipe_to_umh; >struct file *pipe_from_umh; >pid_t pid; > }; > > that GPLed kernel

Re: [PATCH v13 3/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On 05/04/2018 06:12 PM, Ram Pai wrote: >> That new line boils down to: >> >> [ilog2(0)] = "", >> >> on x86. It wasn't *obvious* to me that it is OK to do that. The other >> possibly undefined bits (VM_SOFTDIRTY for instance) #ifdef themselves >> out of this array. >> >> I would

Re: [PATCH v13 3/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On 05/04/2018 06:12 PM, Ram Pai wrote: >> That new line boils down to: >> >> [ilog2(0)] = "", >> >> on x86. It wasn't *obvious* to me that it is OK to do that. The other >> possibly undefined bits (VM_SOFTDIRTY for instance) #ifdef themselves >> out of this array. >> >> I would

Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore

"Paul E. McKenney" writes: > On Fri, May 04, 2018 at 03:08:40PM -0500, Eric W. Biederman wrote: >> "Paul E. McKenney" writes: >> >> > On Fri, May 04, 2018 at 02:03:04PM -0500, Eric W. Biederman wrote: >> >> "Paul E. McKenney"

Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore

"Paul E. McKenney" writes: > On Fri, May 04, 2018 at 03:08:40PM -0500, Eric W. Biederman wrote: >> "Paul E. McKenney" writes: >> >> > On Fri, May 04, 2018 at 02:03:04PM -0500, Eric W. Biederman wrote: >> >> "Paul E. McKenney" writes: >> >> >> >> > On Fri, May 04, 2018 at 12:17:20PM -0500,

Re: *alloc API changes

On Fri, May 04, 2018 at 08:46:46PM -0700, Matthew Wilcox wrote: > On Fri, May 04, 2018 at 06:08:23PM -0700, Kees Cook wrote: > > The number of permutations for our various allocation function is > > rather huge. Currently, it is: > > > > system or wrapper: > > kmem_cache_alloc, kmalloc, vmalloc,

Re: *alloc API changes

On Fri, May 04, 2018 at 08:46:46PM -0700, Matthew Wilcox wrote: > On Fri, May 04, 2018 at 06:08:23PM -0700, Kees Cook wrote: > > The number of permutations for our various allocation function is > > rather huge. Currently, it is: > > > > system or wrapper: > > kmem_cache_alloc, kmalloc, vmalloc,

Re: INFO: task hung in blk_freeze_queue

A patch for this specific report is ready. I don't know whether other "dup" reports will be solved by this patch. Thus, I "undup" this report. #syz undup >From eed54c6ae475860a9c63b37b58f34735e792eef7 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Sat, 5

Re: INFO: task hung in blk_freeze_queue

A patch for this specific report is ready. I don't know whether other "dup" reports will be solved by this patch. Thus, I "undup" this report. #syz undup >From eed54c6ae475860a9c63b37b58f34735e792eef7 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Sat, 5 May 2018 12:59:12 +0900 Subject:

Re: INFO: task hung in blk_freeze_queue

syzbot has found a reproducer for the following crash on: HEAD commit:cdface520934 Merge tag 'for_linus_stable' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=136c8ee780 kernel config:

Re: INFO: task hung in blk_freeze_queue

syzbot has found a reproducer for the following crash on: HEAD commit:cdface520934 Merge tag 'for_linus_stable' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=136c8ee780 kernel config:

Re: *alloc API changes

On Fri, May 4, 2018 at 8:46 PM, Matthew Wilcox wrote: > and if you're counting f2fs_*alloc, there's a metric tonne of *alloc > wrappers out there. Yeah. *sob* > That's a little revisionist ;-) We had kmalloc before we had the slab > allocator (kernel 1.2, I think?). But I

Re: *alloc API changes

On Fri, May 4, 2018 at 8:46 PM, Matthew Wilcox wrote: > and if you're counting f2fs_*alloc, there's a metric tonne of *alloc > wrappers out there. Yeah. *sob* > That's a little revisionist ;-) We had kmalloc before we had the slab > allocator (kernel 1.2, I think?). But I see your point, and

Re: [Ksummit-discuss] bug-introducing patches

On Fri, May 04, 2018 at 07:35:42PM -0400, Theodore Y. Ts'o wrote: > On Fri, May 04, 2018 at 09:51:14PM +, Sasha Levin wrote: > > I don't have an objection to moving this to it's own tag. It will make > > my scripts somewhat simpler for sure. > > It's not a matter "moving this it's own tag",

Re: [Ksummit-discuss] bug-introducing patches

On Fri, May 04, 2018 at 07:35:42PM -0400, Theodore Y. Ts'o wrote: > On Fri, May 04, 2018 at 09:51:14PM +, Sasha Levin wrote: > > I don't have an objection to moving this to it's own tag. It will make > > my scripts somewhat simpler for sure. > > It's not a matter "moving this it's own tag",

[PATCH] HID: uhid: fix a missing-check bug

In uhid_event_from_user(), if it is in_compat_syscall(), the 'type' of the event is first fetched from the 'buffer' in userspace and checked. If the 'type' is UHID_CREATE, it is a messed up request with compat pointer, which could be more than 256 bytes, so it is better allocated from the heap, as

[PATCH] HID: uhid: fix a missing-check bug

In uhid_event_from_user(), if it is in_compat_syscall(), the 'type' of the event is first fetched from the 'buffer' in userspace and checked. If the 'type' is UHID_CREATE, it is a messed up request with compat pointer, which could be more than 256 bytes, so it is better allocated from the heap, as

Re: [PATCH] percpu_ida: Use _irqsave() instead of local_irq_save() + spin_lock

On Fri, May 04, 2018 at 04:22:16PM -0700, Andrew Morton wrote: > I'm feeling a bit hostile toward lib/percpu_ida.c in general ;) It has > very few users and seems rather complicated (what's with that > schedule() in percpu_ida_alloc?). I'm suspecting and hoping that if > someone can figure out

Re: [PATCH] percpu_ida: Use _irqsave() instead of local_irq_save() + spin_lock

On Fri, May 04, 2018 at 04:22:16PM -0700, Andrew Morton wrote: > I'm feeling a bit hostile toward lib/percpu_ida.c in general ;) It has > very few users and seems rather complicated (what's with that > schedule() in percpu_ida_alloc?). I'm suspecting and hoping that if > someone can figure out

Re: [PATCH v1] clk: qcom: gdsc: Add support to poll CFG register to check GDSC state

Yeah sure Stephen. On 5/5/2018 8:21 AM, Stephen Boyd wrote: Quoting Taniya Das (2018-05-03 02:09:57) Hello Stephen, I have tested the below patch & didn't see any issues. Alright. Thanks! Can I take that as a "Tested-by"? -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc.

Re: [PATCH v4 2/3] drm/panel: Add Ilitek ILI9881c panel driver

Hi Maxime, I love your patch! Perhaps something to improve: [auto build test WARNING on ] url: https://github.com/0day-ci/linux/commits/Maxime-Ripard/drm-panel-Add-Ilitek-ILI9881c-controller-driver/20180505-104031 base: config: sh-allmodconfig (attached as .config) compiler:

Re: [PATCH v1] clk: qcom: gdsc: Add support to poll CFG register to check GDSC state

Yeah sure Stephen. On 5/5/2018 8:21 AM, Stephen Boyd wrote: Quoting Taniya Das (2018-05-03 02:09:57) Hello Stephen, I have tested the below patch & didn't see any issues. Alright. Thanks! Can I take that as a "Tested-by"? -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc.

Re: [PATCH v4 2/3] drm/panel: Add Ilitek ILI9881c panel driver

Hi Maxime, I love your patch! Perhaps something to improve: [auto build test WARNING on ] url: https://github.com/0day-ci/linux/commits/Maxime-Ripard/drm-panel-Add-Ilitek-ILI9881c-controller-driver/20180505-104031 base: config: sh-allmodconfig (attached as .config) compiler:

Re: *alloc API changes

On Fri, May 04, 2018 at 06:08:23PM -0700, Kees Cook wrote: > The number of permutations for our various allocation function is > rather huge. Currently, it is: > > system or wrapper: > kmem_cache_alloc, kmalloc, vmalloc, kvmalloc, devm_kmalloc, > dma_alloc_coherent, pci_alloc_consistent,

Re: *alloc API changes

On Fri, May 04, 2018 at 06:08:23PM -0700, Kees Cook wrote: > The number of permutations for our various allocation function is > rather huge. Currently, it is: > > system or wrapper: > kmem_cache_alloc, kmalloc, vmalloc, kvmalloc, devm_kmalloc, > dma_alloc_coherent, pci_alloc_consistent,

[PATCH] [v6] staging: wlan-ng: prism2sta: fix indent coding-style issues

Fixed format/style issues found with checkpatch. No code changes. Corrected alignment of variables after open parenthesis and line breaks. Checkpatch now returns clean except for "line over 80 char" warnings. Signed-off-by: Efstratios Gavas --- v2(unlabeled): changed title info v3:

[PATCH] [v6] staging: wlan-ng: prism2sta: fix indent coding-style issues

Fixed format/style issues found with checkpatch. No code changes. Corrected alignment of variables after open parenthesis and line breaks. Checkpatch now returns clean except for "line over 80 char" warnings. Signed-off-by: Efstratios Gavas --- v2(unlabeled): changed title info v3: improved

Re: [PATCH v6 1/3] clk: qcom: Configure the RCGs to a safe source as needed

Quoting Amit Nischal (2018-05-03 04:57:37) > On 2018-05-02 13:15, Stephen Boyd wrote: > > Quoting Amit Nischal (2018-04-30 09:20:08) > > > >> +} > >> + > >> +static void clk_rcg2_shared_disable(struct clk_hw *hw) > >> +{ > >> + struct clk_rcg2 *rcg = to_clk_rcg2(hw); > >> + struct

Re: [PATCH v6 1/3] clk: qcom: Configure the RCGs to a safe source as needed

Quoting Amit Nischal (2018-05-03 04:57:37) > On 2018-05-02 13:15, Stephen Boyd wrote: > > Quoting Amit Nischal (2018-04-30 09:20:08) > > > >> +} > >> + > >> +static void clk_rcg2_shared_disable(struct clk_hw *hw) > >> +{ > >> + struct clk_rcg2 *rcg = to_clk_rcg2(hw); > >> + struct

Re: [PATCH v6 3/3] clk: qcom: Add Global Clock controller (GCC) driver for SDM845

Quoting Amit Nischal (2018-05-04 03:45:12) > On 2018-05-02 12:53, Stephen Boyd wrote: > > Quoting Amit Nischal (2018-04-30 09:20:10) > >> + > >> +static struct clk_branch gcc_disp_gpll0_clk_src = { > >> + .halt_reg = 0x52004, > >> + .halt_check = BRANCH_HALT_DELAY, > > > > What about

Re: [PATCH v6 3/3] clk: qcom: Add Global Clock controller (GCC) driver for SDM845

Quoting Amit Nischal (2018-05-04 03:45:12) > On 2018-05-02 12:53, Stephen Boyd wrote: > > Quoting Amit Nischal (2018-04-30 09:20:10) > >> + > >> +static struct clk_branch gcc_disp_gpll0_clk_src = { > >> + .halt_reg = 0x52004, > >> + .halt_check = BRANCH_HALT_DELAY, > > > > What about

Re: [PATCH v3 1/2] clk: x86: Add ST oscout platform clock

Quoting Akshu Agrawal (2018-05-04 10:07:18) > Stoney SoC provides oscout clock. This clock can support 25Mhz and > 48Mhz of frequency. > The clock is available for general system use. > > Signed-off-by: Akshu Agrawal > --- > v2: config change, added SPDX tag and used

Re: [PATCH v3 1/2] clk: x86: Add ST oscout platform clock

Quoting Akshu Agrawal (2018-05-04 10:07:18) > Stoney SoC provides oscout clock. This clock can support 25Mhz and > 48Mhz of frequency. > The clock is available for general system use. > > Signed-off-by: Akshu Agrawal > --- > v2: config change, added SPDX tag and used clk_hw_register_. > v3: Fix

Re: [PATCH V3 1/2] clk: imx6sx: add missing lvds2 clock to the clock tree

Quoting Anson Huang (2018-04-20 00:38:10) > i.MX6SX has lvds2 (analog clock2), an I/O clock like lvds1. > And this lvds2, along with lvds1, can be used to provide > external clock source to the internal pll, such as pll4_audio > and pll5_video. > > This patch mainly adds the lvds2 to the clock

Re: [PATCH V3 1/2] clk: imx6sx: add missing lvds2 clock to the clock tree

Quoting Anson Huang (2018-04-20 00:38:10) > i.MX6SX has lvds2 (analog clock2), an I/O clock like lvds1. > And this lvds2, along with lvds1, can be used to provide > external clock source to the internal pll, such as pll4_audio > and pll5_video. > > This patch mainly adds the lvds2 to the clock

Re: [PATCH 6/9] firmware: print firmware name on fallback path

On 2018-05-03 07:42 PM, Luis R. Rodriguez wrote: On Mon, Apr 23, 2018 at 04:12:02PM -0400, Andres Rodriguez wrote: Previously, one could assume the firmware name from the preceding message: "Direct firmware load for {name} failed with error %d". However, with the new

Re: [PATCH 6/9] firmware: print firmware name on fallback path

On 2018-05-03 07:42 PM, Luis R. Rodriguez wrote: On Mon, Apr 23, 2018 at 04:12:02PM -0400, Andres Rodriguez wrote: Previously, one could assume the firmware name from the preceding message: "Direct firmware load for {name} failed with error %d". However, with the new

Re: [PATCH] clk: imx6ul: fix periph clk2 clock mux selection

Quoting Stefan Agner (2018-04-18 05:52:54) > According to the data sheet the 3rd choice is the bypass clock > of pll2. This should not have any effect in practice as this > selection is not used currently. > > Signed-off-by: Stefan Agner > --- Applied to clk-next

Re: [PATCH] clk: imx6ul: fix periph clk2 clock mux selection

Quoting Stefan Agner (2018-04-18 05:52:54) > According to the data sheet the 3rd choice is the bypass clock > of pll2. This should not have any effect in practice as this > selection is not used currently. > > Signed-off-by: Stefan Agner > --- Applied to clk-next

Re: [PATCH v1] clk: qcom: gdsc: Add support to poll CFG register to check GDSC state

Quoting Taniya Das (2018-05-03 02:09:57) > Hello Stephen, > > I have tested the below patch & didn't see any issues. Alright. Thanks! Can I take that as a "Tested-by"?

Re: [PATCH v1] clk: qcom: gdsc: Add support to poll CFG register to check GDSC state

Quoting Taniya Das (2018-05-03 02:09:57) > Hello Stephen, > > I have tested the below patch & didn't see any issues. Alright. Thanks! Can I take that as a "Tested-by"?

Re: [RESEND PATCH] clk: stm32: fix: stm32 clock drivers are not compiled by default

Quoting Alexandre Torgue (2018-05-04 00:54:16) > Stephen > > On 05/03/2018 08:40 AM, gabriel.fernan...@st.com wrote: > > From: Gabriel Fernandez > > > > Clock driver is mandatory if the machine is selected. > > Then don't use 'bool' and 'depends on' commands, but

Re: [RESEND PATCH] clk: stm32: fix: stm32 clock drivers are not compiled by default

Quoting Alexandre Torgue (2018-05-04 00:54:16) > Stephen > > On 05/03/2018 08:40 AM, gabriel.fernan...@st.com wrote: > > From: Gabriel Fernandez > > > > Clock driver is mandatory if the machine is selected. > > Then don't use 'bool' and 'depends on' commands, but 'def_bool' > > with the

Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features

On Fri, 4 May 2018 12:06:42 -0400 Steven Rostedt wrote: > On Sat, 5 May 2018 00:48:28 +0900 > Masami Hiramatsu wrote: > > > So the syntax will be > > > > p[:EVENT] SYM[(CAST)|+OFFS] [FETCHARG] > > > > And here is an example; > > > > p:myevent

Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features

On Fri, 4 May 2018 12:06:42 -0400 Steven Rostedt wrote: > On Sat, 5 May 2018 00:48:28 +0900 > Masami Hiramatsu wrote: > > > So the syntax will be > > > > p[:EVENT] SYM[(CAST)|+OFFS] [FETCHARG] > > > > And here is an example; > > > > p:myevent vfs_read(void *file, char *buf, size_t count,

Re: [v2 PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats

On 05/03/2018 01:04 PM, Michael Chan wrote: On Wed, May 2, 2018 at 5:30 PM, Zumeng Chen wrote: On 2018年05月03日 01:32, Michael Chan wrote: On Wed, May 2, 2018 at 3:27 AM, Zumeng Chen wrote: On 2018年05月02日 13:12, Michael Chan wrote: On Tue, May 1,

Re: [v2 PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats

On 05/03/2018 01:04 PM, Michael Chan wrote: On Wed, May 2, 2018 at 5:30 PM, Zumeng Chen wrote: On 2018年05月03日 01:32, Michael Chan wrote: On Wed, May 2, 2018 at 3:27 AM, Zumeng Chen wrote: On 2018年05月02日 13:12, Michael Chan wrote: On Tue, May 1, 2018 at 5:42 PM, Zumeng Chen wrote: diff

Re: [PATCH 1/2] tpm: do not suspend/resume if power stays on

On Wed, May 02, 2018 at 05:38:28PM +0300, Jarkko Sakkinen wrote: > From: Enric Balletbo i Serra > > commit b5d0ebc99bf5d0801a5ecbe958caa3d68b8eaee8 upstream > > The suspend/resume behavior of the TPM can be controlled by setting > "powered-while-suspended" in the

Re: [PATCH 1/2] tpm: do not suspend/resume if power stays on

On Wed, May 02, 2018 at 05:38:28PM +0300, Jarkko Sakkinen wrote: > From: Enric Balletbo i Serra > > commit b5d0ebc99bf5d0801a5ecbe958caa3d68b8eaee8 upstream > > The suspend/resume behavior of the TPM can be controlled by setting > "powered-while-suspended" in the DTS. This is useful for the

Re: [PATCH v2] clk: x86: Add ST oscout platform clock

Quoting Akshu Agrawal (2018-05-03 01:30:26) > diff --git a/drivers/clk/x86/Makefile b/drivers/clk/x86/Makefile > index 1367afb..2aee002 100644 > --- a/drivers/clk/x86/Makefile > +++ b/drivers/clk/x86/Makefile > @@ -1,3 +1,4 @@ > clk-x86-lpss-objs := clk-lpt.o >

Re: [PATCH v2] clk: x86: Add ST oscout platform clock

Quoting Akshu Agrawal (2018-05-03 01:30:26) > diff --git a/drivers/clk/x86/Makefile b/drivers/clk/x86/Makefile > index 1367afb..2aee002 100644 > --- a/drivers/clk/x86/Makefile > +++ b/drivers/clk/x86/Makefile > @@ -1,3 +1,4 @@ > clk-x86-lpss-objs := clk-lpt.o >

[RESEND PATCH 5/5] usb: mtu3: make USB_MTU3_DUAL_ROLE depend on EXTCON but not USB_MTU3

In fact the driver depends on EXTCON only when it's configed as USB_MTU3_DUAL_ROLE, so make USB_MTU3_DUAL_ROLE depend on EXTCON but not USB_MTU3. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

[RESEND PATCH 1/5] usb: mtu3: avoid TX data length truncated in SS/SSP mode

The variable of 'count' is declared as u8, this will cause an issue due to value truncated when works in SS or SSP mode and data length is greater than 255, so change it as u32. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget_ep0.c | 2 +- 1 file changed,

[RESEND PATCH 4/5] usb: mtu3: fix operation failure when test TEST_J/K

There is an error dialog popped up in PC when test TEST_J/K by EHSETT tool, due to not waiting for the completion of control transfer. Here fix it by entering test mode after Status Stage finish. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget_ep0.c | 10

[RESEND PATCH 5/5] usb: mtu3: make USB_MTU3_DUAL_ROLE depend on EXTCON but not USB_MTU3

In fact the driver depends on EXTCON only when it's configed as USB_MTU3_DUAL_ROLE, so make USB_MTU3_DUAL_ROLE depend on EXTCON but not USB_MTU3. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[RESEND PATCH 1/5] usb: mtu3: avoid TX data length truncated in SS/SSP mode

The variable of 'count' is declared as u8, this will cause an issue due to value truncated when works in SS or SSP mode and data length is greater than 255, so change it as u32. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget_ep0.c | 2 +- 1 file changed, 1 insertion(+), 1

[RESEND PATCH 4/5] usb: mtu3: fix operation failure when test TEST_J/K

There is an error dialog popped up in PC when test TEST_J/K by EHSETT tool, due to not waiting for the completion of control transfer. Here fix it by entering test mode after Status Stage finish. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget_ep0.c | 10 ++ 1 file changed,

[RESEND PATCH 3/5] usb: mtu3: fix an unrecognized issue when connected with PC

When boot on the platform with the USB cable connected to Win7, the Win7 will pop up an error dialog: "USB Device not recognized", but finally the Win7 can enumerate it successfully. The root cause is as the following: When the xHCI driver set PORT_POWER of the OTG port, and if both IDPIN and

[RESEND PATCH 3/5] usb: mtu3: fix an unrecognized issue when connected with PC

When boot on the platform with the USB cable connected to Win7, the Win7 will pop up an error dialog: "USB Device not recognized", but finally the Win7 can enumerate it successfully. The root cause is as the following: When the xHCI driver set PORT_POWER of the OTG port, and if both IDPIN and

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 2018/5/5 2:59, Jaegeuk Kim wrote: > On 05/02, Chao Yu wrote: >> On 2018/4/28 10:36, Jaegeuk Kim wrote: >>> On 04/27, Chao Yu wrote: On 2018/4/27 0:03, Jaegeuk Kim wrote: > On 04/24, Chao Yu wrote: >> Thread A Thread BThread C >> - f2fs_remount

[RESEND PATCH 2/5] usb: mtu3: remove repeated setting of gadget state

The usb_add_gadget_udc() will set the gadget state as USB_STATE_NOTATTACHED, so we needn't set it again. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 2018/5/5 2:59, Jaegeuk Kim wrote: > On 05/02, Chao Yu wrote: >> On 2018/4/28 10:36, Jaegeuk Kim wrote: >>> On 04/27, Chao Yu wrote: On 2018/4/27 0:03, Jaegeuk Kim wrote: > On 04/24, Chao Yu wrote: >> Thread A Thread BThread C >> - f2fs_remount

[RESEND PATCH 2/5] usb: mtu3: remove repeated setting of gadget state

The usb_add_gadget_udc() will set the gadget state as USB_STATE_NOTATTACHED, so we needn't set it again. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/usb/mtu3/mtu3_gadget.c

[PATCH v2 2/2] phy: mediatek: add XS-PHY driver

Support XS-PHY for MediaTek SoCs with USB3.1 GEN2 controller Signed-off-by: Chunfeng Yun --- drivers/phy/mediatek/Kconfig |9 + drivers/phy/mediatek/Makefile|1 + drivers/phy/mediatek/phy-mtk-xsphy.c | 600 ++ 3

[PATCH v2 2/2] phy: mediatek: add XS-PHY driver

Support XS-PHY for MediaTek SoCs with USB3.1 GEN2 controller Signed-off-by: Chunfeng Yun --- drivers/phy/mediatek/Kconfig |9 + drivers/phy/mediatek/Makefile|1 + drivers/phy/mediatek/phy-mtk-xsphy.c | 600 ++ 3 files changed, 610

[PATCH v2 1/2] dt-bindings: add MediaTek XS-PHY binding

Add a DT binding documentation of XS-PHY for MediaTek SoCs with USB3.1 GEN2 controller Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/phy/phy-mtk-xsphy.txt | 110 1 file changed, 110 insertions(+) create mode 100644

[PATCH v2 1/2] dt-bindings: add MediaTek XS-PHY binding

Add a DT binding documentation of XS-PHY for MediaTek SoCs with USB3.1 GEN2 controller Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/phy/phy-mtk-xsphy.txt | 110 1 file changed, 110 insertions(+) create mode 100644

[PATCH v2 0/2] Add MediaTek XS-PHY driver

>From a0814ad7725587a06d273997e0fdf5161f916fd8 Mon Sep 17 00:00:00 2001 From: Chunfeng Yun Date: Sat, 5 May 2018 09:56:59 +0800 Subject: [PATCH v2 0/2] Add MediaTek XS-PHY driver This patch series support the SuperSpeedPlus XS-PHY transceiver for USB3.1 GEN2 controller

[PATCH v2 0/2] Add MediaTek XS-PHY driver

>From a0814ad7725587a06d273997e0fdf5161f916fd8 Mon Sep 17 00:00:00 2001 From: Chunfeng Yun Date: Sat, 5 May 2018 09:56:59 +0800 Subject: [PATCH v2 0/2] Add MediaTek XS-PHY driver This patch series support the SuperSpeedPlus XS-PHY transceiver for USB3.1 GEN2 controller on MediaTek chips. The

RE: [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages

> On Fri 04-05-18 14:52:09, Huaisheng Ye wrote: > > realtotalpages is calculated by taking off absent_pages from > > spanned_pages in every zone. > > Debug message of calculate_node_totalpages shall accurately > > indicate that it is real totalpages to avoid ambiguity. > > Is the printk actually

RE: [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages

> On Fri 04-05-18 14:52:09, Huaisheng Ye wrote: > > realtotalpages is calculated by taking off absent_pages from > > spanned_pages in every zone. > > Debug message of calculate_node_totalpages shall accurately > > indicate that it is real totalpages to avoid ambiguity. > > Is the printk actually

[GIT PULL] Kbuild fixes for 4.17-rc4

Hi Linus, Please pull some Kbuild fixes. Thanks! The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64: Linux v4.17-rc3 (2018-04-29 14:17:42 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git

[GIT PULL] Kbuild fixes for 4.17-rc4

Hi Linus, Please pull some Kbuild fixes. Thanks! The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64: Linux v4.17-rc3 (2018-04-29 14:17:42 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git

Re: Oops on the system startup in the function part_in_flight()

On 5/4/18 6:35 PM, Ben Greear wrote: > Hello, > > I am trying to bisect a pktgen related performance regression that appears to > be between the 4.13 and 4.14 kernels. But, my system keeps crashing due to > part_in_flight > oops so bisecting is not going well. > > It looks like this oops was

Re: Oops on the system startup in the function part_in_flight()

On 5/4/18 6:35 PM, Ben Greear wrote: > Hello, > > I am trying to bisect a pktgen related performance regression that appears to > be between the 4.13 and 4.14 kernels. But, my system keeps crashing due to > part_in_flight > oops so bisecting is not going well. > > It looks like this oops was

[GIT PULL] clk fixes for v4.17-rc3

From: Stephen Boyd The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for

[GIT PULL] clk fixes for v4.17-rc3

From: Stephen Boyd The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to fetch

Re: I2C PM overhaul needed? (Re: [PATCH 1/2] i2c: sprd: Prevent i2c accesses after suspend is called)

On Fri, May 04, 2018 at 02:24:47PM +0200, Wolfram Sang wrote: > To handle that, I imagined an additional adapter callback like > 'master_xfer_irqless' to be used for such special I2C messages. These > kind of special messages could be tagged with a new I2C_M_something > flag. > And maybe this

Re: I2C PM overhaul needed? (Re: [PATCH 1/2] i2c: sprd: Prevent i2c accesses after suspend is called)

On Fri, May 04, 2018 at 02:24:47PM +0200, Wolfram Sang wrote: > To handle that, I imagined an additional adapter callback like > 'master_xfer_irqless' to be used for such special I2C messages. These > kind of special messages could be tagged with a new I2C_M_something > flag. > And maybe this

Re: [PATCH 21/24] selftests: memfd: return Kselftest Skip code for skipped tests

On 05/04/2018 06:13 PM, Shuah Khan (Samsung OSG) wrote: > When memfd test is skipped because of unmet dependencies and/or unsupported > configuration, it returns non-zero value which is treated as a fail by the > Kselftest framework. This leads to false negative result even when the test > could

Re: [PATCH 21/24] selftests: memfd: return Kselftest Skip code for skipped tests

On 05/04/2018 06:13 PM, Shuah Khan (Samsung OSG) wrote: > When memfd test is skipped because of unmet dependencies and/or unsupported > configuration, it returns non-zero value which is treated as a fail by the > Kselftest framework. This leads to false negative result even when the test > could

  1   2   3   4   5   6   7   8   9   10   >