Hi Will,
Just curious to know, is there anything that I should be addressing
in these patches ? For now, I don't see anything from my side that
requires modification, unless one has some more review comments on
this.
Status so far on and around this:
- Status of Toshi's series of patches is
Hi Will,
Just curious to know, is there anything that I should be addressing
in these patches ? For now, I don't see anything from my side that
requires modification, unless one has some more review comments on
this.
Status so far on and around this:
- Status of Toshi's series of patches is
FYI, we noticed the following commit (built with gcc-7):
commit: 2d251ff6e66d7978b3e7a9c69e99b7150de26926 ("mm, oom: fix unnecessary
killing of additional processes")
url:
FYI, we noticed the following commit (built with gcc-7):
commit: 2d251ff6e66d7978b3e7a9c69e99b7150de26926 ("mm, oom: fix unnecessary
killing of additional processes")
url:
Hi,
On Saturday 02 June 2018 12:02 PM, Stephen Boyd wrote:
> Quoting Faiz Abbas (2018-05-30 07:11:32)
>> diff --git a/arch/arm/boot/dts/dra76x.dtsi b/arch/arm/boot/dts/dra76x.dtsi
>> index bfc82636999c..57b8dc0fe719 100644
>> --- a/arch/arm/boot/dts/dra76x.dtsi
>> +++
Hi,
On Saturday 02 June 2018 12:02 PM, Stephen Boyd wrote:
> Quoting Faiz Abbas (2018-05-30 07:11:32)
>> diff --git a/arch/arm/boot/dts/dra76x.dtsi b/arch/arm/boot/dts/dra76x.dtsi
>> index bfc82636999c..57b8dc0fe719 100644
>> --- a/arch/arm/boot/dts/dra76x.dtsi
>> +++
From: Hoeun Ryu
Many console device drivers hold the uart_port->lock spinlock with irq enabled
(using spin_lock()) while the device drivers are writing characters to their
devices,
but the device drivers just try to hold the spin lock (using spin_trylock()) if
"oops_in_progress" is equal or
From: Hoeun Ryu
Many console device drivers hold the uart_port->lock spinlock with irq enabled
(using spin_lock()) while the device drivers are writing characters to their
devices,
but the device drivers just try to hold the spin lock (using spin_trylock()) if
"oops_in_progress" is equal or
On Fri, 11 May 2018, Charles Keepax wrote:
> Some Arizona CODECs have a small timing window where they will
> NAK an I2C transaction if it happens before the boot done bit is
> set. This can cause the read of the register containing the boot
> done bit to fail until it is set. Since
On Fri, 11 May 2018, Charles Keepax wrote:
> Some Arizona CODECs have a small timing window where they will
> NAK an I2C transaction if it happens before the boot done bit is
> set. This can cause the read of the register containing the boot
> done bit to fail until it is set. Since
This adds prepare/unprepare/is_prepared functionality to the drivers for
the SI544 and SI514 chips, allowing the clock output to be disabled when
the clock is not in use.
Signed-off-by: Mike Looijmans
---
drivers/clk/clk-si514.c | 38 +-
This adds prepare/unprepare/is_prepared functionality to the drivers for
the SI544 and SI514 chips, allowing the clock output to be disabled when
the clock is not in use.
Signed-off-by: Mike Looijmans
---
drivers/clk/clk-si514.c | 38 +-
On Fri, 01 Jun 2018, Andy Shevchenko wrote:
> On Fri, 2018-05-18 at 14:51 +0100, Lee Jones wrote:
> > On Tue, 24 Apr 2018, Andy Shevchenko wrote:
> >
> > > According to documentation REMAP register has to be programmed in
> > > either DMA or PIO mode of the slice.
> > >
> > > Move the DMA
On Fri, 01 Jun 2018, Andy Shevchenko wrote:
> On Fri, 2018-05-18 at 14:51 +0100, Lee Jones wrote:
> > On Tue, 24 Apr 2018, Andy Shevchenko wrote:
> >
> > > According to documentation REMAP register has to be programmed in
> > > either DMA or PIO mode of the slice.
> > >
> > > Move the DMA
On Tue, 24 Apr 2018, Andy Shevchenko wrote:
> According to documentation the function has 2 bits for reset
> while iDMA 64-bit has only one.
>
> Rename it accordingly. Note, there is no functional change since
> we always handle them together.
>
> Signed-off-by: Andy Shevchenko
> ---
>
On Tue, 24 Apr 2018, Andy Shevchenko wrote:
> According to documentation the function has 2 bits for reset
> while iDMA 64-bit has only one.
>
> Rename it accordingly. Note, there is no functional change since
> we always handle them together.
>
> Signed-off-by: Andy Shevchenko
> ---
>
Hello,
syzbot found the following crash on:
HEAD commit:325e14f97e0c Merge branch 'fixes' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166329d780
kernel config: https://syzkaller.appspot.com/x/.config?x=968b0b23c7854c0b
Hello,
syzbot found the following crash on:
HEAD commit:325e14f97e0c Merge branch 'fixes' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166329d780
kernel config: https://syzkaller.appspot.com/x/.config?x=968b0b23c7854c0b
On Mon, May 21, 2018 at 11:55 PM, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
>
On Mon, May 21, 2018 at 11:55 PM, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
>
Hi Paul,
I was testing RCU boosting behavior with rcutorture on rcu/dev and I had some
issues getting it to fail when no RCU boost is done (CONFIG_RCU_BOOST is
disabled and rcutorture is forced to test it using test_boost parameter).
It appears I need to disable RT throttling so that the readers
Hi Paul,
I was testing RCU boosting behavior with rcutorture on rcu/dev and I had some
issues getting it to fail when no RCU boost is done (CONFIG_RCU_BOOST is
disabled and rcutorture is forced to test it using test_boost parameter).
It appears I need to disable RT throttling so that the readers
On Mon, Jun 04, 2018 at 10:41:10AM +0800, 禹舟键 wrote:
> Hi Tetsuo
> > Since origin_memcg_name is printed for both memcg OOM and !memcg OOM, it is
> > strange that origin_memcg_name is updated only when memcg != NULL. Have you
> > really tested !memcg OOM case?
>
> if memcg == NULL ,
On Mon, Jun 04, 2018 at 10:41:10AM +0800, 禹舟键 wrote:
> Hi Tetsuo
> > Since origin_memcg_name is printed for both memcg OOM and !memcg OOM, it is
> > strange that origin_memcg_name is updated only when memcg != NULL. Have you
> > really tested !memcg OOM case?
>
> if memcg == NULL ,
Hi Linus,
Please pull these rslib changes for v4.18-rc1. Thomas asked me to carry
this series since I've been coordinating VLA removal, and he's got enough
trees to worry about. :) This has been in -next for a while now.
Thanks!
-Kees
The following changes since commit
Hi Linus,
Please pull these rslib changes for v4.18-rc1. Thomas asked me to carry
this series since I've been coordinating VLA removal, and he's got enough
trees to worry about. :) This has been in -next for a while now.
Thanks!
-Kees
The following changes since commit
On Sun, Jun 3, 2018 at 3:31 AM, Matthew Wilcox wrote:
> On Sun, Jun 03, 2018 at 01:34:07AM +0530, Souptick Joarder wrote:
>> @@ -3570,9 +3571,8 @@ static int hugetlb_cow(struct mm_struct *mm, struct
>> vm_area_struct *vma,
>> return 0;
>> }
>>
>> -
On Sun, Jun 3, 2018 at 3:31 AM, Matthew Wilcox wrote:
> On Sun, Jun 03, 2018 at 01:34:07AM +0530, Souptick Joarder wrote:
>> @@ -3570,9 +3571,8 @@ static int hugetlb_cow(struct mm_struct *mm, struct
>> vm_area_struct *vma,
>> return 0;
>> }
>>
>> -
On 06/02/2018 04:41 PM, Amit Kucheria wrote:
> status_field and trdy are unused in any of the tsens drivers. Remove them.
>
> Signed-off-by: Amit Kucheria
Acked-by: Rajendra Nayak
> ---
> drivers/thermal/qcom/tsens.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git
On 06/02/2018 04:41 PM, Amit Kucheria wrote:
> status_field and trdy are unused in any of the tsens drivers. Remove them.
>
> Signed-off-by: Amit Kucheria
Acked-by: Rajendra Nayak
> ---
> drivers/thermal/qcom/tsens.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git
On 06/02/2018 04:41 PM, Amit Kucheria wrote:
> There are two tsens blocks on the SDM845. These will be configured through
> the devicetree.
>
> Signed-off-by: Amit Kucheria
> ---
> .../devicetree/bindings/thermal/qcom-tsens.txt | 1 +
> drivers/thermal/qcom/Makefile
On 06/02/2018 04:41 PM, Amit Kucheria wrote:
> There are two tsens blocks on the SDM845. These will be configured through
> the devicetree.
>
> Signed-off-by: Amit Kucheria
> ---
> .../devicetree/bindings/thermal/qcom-tsens.txt | 1 +
> drivers/thermal/qcom/Makefile
Linus,
Please pull the userns-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
userns-linus
HEAD: f3f1a18330ac1b717cd7a32adff38d965f365aa2 fs: Allow CAP_SYS_ADMIN in
s_user_ns to freeze and thaw filesystems
Apologies for the
Linus,
Please pull the userns-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
userns-linus
HEAD: f3f1a18330ac1b717cd7a32adff38d965f365aa2 fs: Allow CAP_SYS_ADMIN in
s_user_ns to freeze and thaw filesystems
Apologies for the
Linus,
Please pull the siginfo-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
siginfo-linus
HEAD: 26da35010c6d6ce317d511c8186585bdd8ab6629 signal/sh: Stop gcc warning
about an impossible case in do_divide_error
Apologies for
Hi Colin,
On Fri, Nov 24, 2017 at 01:37:41PM +, Colin King wrote:
> From: Colin Ian King
>
> Use setup_timer function instead of initializing timer with the
> function and data fields.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/nfc/st21nfca/se.c | 10 --
> 1 file changed,
Linus,
Please pull the siginfo-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
siginfo-linus
HEAD: 26da35010c6d6ce317d511c8186585bdd8ab6629 signal/sh: Stop gcc warning
about an impossible case in do_divide_error
Apologies for
Hi Colin,
On Fri, Nov 24, 2017 at 01:37:41PM +, Colin King wrote:
> From: Colin Ian King
>
> Use setup_timer function instead of initializing timer with the
> function and data fields.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/nfc/st21nfca/se.c | 10 --
> 1 file changed,
Linus,
Please pull the siginfo-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
siginfo-linus
HEAD: 26da35010c6d6ce317d511c8186585bdd8ab6629 signal/sh: Stop gcc warning
about an impossible case in do_divide_error
This set of
Linus,
Please pull the siginfo-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
siginfo-linus
HEAD: 26da35010c6d6ce317d511c8186585bdd8ab6629 signal/sh: Stop gcc warning
about an impossible case in do_divide_error
This set of
Linus,
Please pull the userns-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
userns-linus
HEAD: f3f1a18330ac1b717cd7a32adff38d965f365aa2 fs: Allow CAP_SYS_ADMIN in
s_user_ns to freeze and thaw filesystems
This is the last
Linus,
Please pull the userns-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
userns-linus
HEAD: f3f1a18330ac1b717cd7a32adff38d965f365aa2 fs: Allow CAP_SYS_ADMIN in
s_user_ns to freeze and thaw filesystems
This is the last
Hi Linus,
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git
tags/chrome-platform-for-linus-4.18
for you
Hi Stephen,
Thanks for the reply.
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: 02 June 2018 12:11 PM
> To: Rajan Vaja
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Jolly Shah
> ; Michal Simek ;
> mturque...@baylibre.com
> Subject: RE:
Hi Linus,
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git
tags/chrome-platform-for-linus-4.18
for you
Hi Stephen,
Thanks for the reply.
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: 02 June 2018 12:11 PM
> To: Rajan Vaja
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Jolly Shah
> ; Michal Simek ;
> mturque...@baylibre.com
> Subject: RE:
Hello
I have trouble reading the code, I hope you can help guide
The function sata_print_link_status in the file drivers/ata/libata-core.c
checks the return value when the function sata_scr_read is called on line 3009,
but does not check the return value when calling sata_scr_read on line 3011.
Hello
I have trouble reading the code, I hope you can help guide
The function sata_print_link_status in the file drivers/ata/libata-core.c
checks the return value when the function sata_scr_read is called on line 3009,
but does not check the return value when calling sata_scr_read on line 3011.
Hi Rob,
After merging the drm-msm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpu/drm/msm/adreno/a5xx_gpu.o: In function `a5xx_gpu_busy':
a5xx_gpu.c:(.text+0xcc): undefined reference to `__aeabi_uldivmod'
Caused by commit
dd4ff3063899 ("drm/msm:
Hi Rob,
After merging the drm-msm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpu/drm/msm/adreno/a5xx_gpu.o: In function `a5xx_gpu_busy':
a5xx_gpu.c:(.text+0xcc): undefined reference to `__aeabi_uldivmod'
Caused by commit
dd4ff3063899 ("drm/msm:
From: Randy Dunlap
Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure
that other required files are present and to determine build flags
settings, but none of these check that pkg-config itself is present.
Add a check for all 4 of these targets and update
From: Randy Dunlap
Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure
that other required files are present and to determine build flags
settings, but none of these check that pkg-config itself is present.
Add a check for all 4 of these targets and update
If we settime between 1970 and 2000.
for example:
$ date 052915571978
$ hwclock -w
it will be wrong, this patch fix it.
Signed-off-by: Linkui
---
drivers/rtc/rtc-ds1307.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-ds1307.c
If we settime between 1970 and 2000.
for example:
$ date 052915571978
$ hwclock -w
it will be wrong, this patch fix it.
Signed-off-by: Linkui
---
drivers/rtc/rtc-ds1307.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-ds1307.c
Hi Tetsuo
> Since origin_memcg_name is printed for both memcg OOM and !memcg OOM, it is
> strange that origin_memcg_name is updated only when memcg != NULL. Have you
> really tested !memcg OOM case?
if memcg == NULL , origin_memcg_name will also be NULL, so the length
of it is 0.
Hi Tetsuo
> Since origin_memcg_name is printed for both memcg OOM and !memcg OOM, it is
> strange that origin_memcg_name is updated only when memcg != NULL. Have you
> really tested !memcg OOM case?
if memcg == NULL , origin_memcg_name will also be NULL, so the length
of it is 0.
New Centaur CPU support CMCI mechanism, which is compatible with INTEL CMCI.
Signed-off-by: David Wang
Changes from v1 to v2:
*1, add vendor check for Centaur CPU in cmci_supported.
*2, Only call intel_init_cmci for Centaur CPU in mce_intel_feature_init
function.
---
arch/x86/Kconfig
New Centaur CPU support CMCI mechanism, which is compatible with INTEL CMCI.
Signed-off-by: David Wang
Changes from v1 to v2:
*1, add vendor check for Centaur CPU in cmci_supported.
*2, Only call intel_init_cmci for Centaur CPU in mce_intel_feature_init
function.
---
arch/x86/Kconfig
FYI, https://sfconservancy.org/blog/2018/may/18/tesla-incomplete-ccs/
On Sun, Nov 26, 2017 at 8:23 PM, Geunsik Lim wrote:
> Here is my next activity.
>
> After reading http://gpl-violations.org/helping/,
> I have reported this issue to solve a potential GPL misuse about the
> Linux kernel open
FYI, https://sfconservancy.org/blog/2018/may/18/tesla-incomplete-ccs/
On Sun, Nov 26, 2017 at 8:23 PM, Geunsik Lim wrote:
> Here is my next activity.
>
> After reading http://gpl-violations.org/helping/,
> I have reported this issue to solve a potential GPL misuse about the
> Linux kernel open
On Tue, May 29, 2018 at 06:03:32PM +0200, Peter Zijlstra wrote:
> On Mon, Mar 19, 2018 at 03:23:25PM +0800, changbin...@intel.com wrote:
> > From: Changbin Du
> >
> > Inspired by gdb command 'list', show the code context of target lines.
> > Here is a example:
> >
> > $ scripts/faddr2line
On Tue, May 29, 2018 at 06:03:32PM +0200, Peter Zijlstra wrote:
> On Mon, Mar 19, 2018 at 03:23:25PM +0800, changbin...@intel.com wrote:
> > From: Changbin Du
> >
> > Inspired by gdb command 'list', show the code context of target lines.
> > Here is a example:
> >
> > $ scripts/faddr2line
On Wed, May 30, 2018 at 08:01:48AM +1000, NeilBrown wrote:
> On Tue, May 29 2018, Peter Zijlstra wrote:
>
> > On Tue, May 29, 2018 at 12:07:10PM -0500, Josh Poimboeuf wrote:
> >> Yeah, this change really should have been an optional arg. It hurt the
> >> readability and compactness of the
On Wed, May 30, 2018 at 08:01:48AM +1000, NeilBrown wrote:
> On Tue, May 29 2018, Peter Zijlstra wrote:
>
> > On Tue, May 29, 2018 at 12:07:10PM -0500, Josh Poimboeuf wrote:
> >> Yeah, this change really should have been an optional arg. It hurt the
> >> readability and compactness of the
> -Original Mail-
> Sender: Borislav Petkov [mailto:b...@alien8.de]
> Time: 2018年6月1日 17:38
> Receiver: David Wang
> CC: tony.l...@intel.com; mi...@redhat.com; t...@linutronix.de;
> h...@zytor.com; gre...@linuxfoudation.org; x...@kernel.org;
> linux-kernel@vger.kernel.org;
> -Original Mail-
> Sender: Borislav Petkov [mailto:b...@alien8.de]
> Time: 2018年6月1日 17:38
> Receiver: David Wang
> CC: tony.l...@intel.com; mi...@redhat.com; t...@linutronix.de;
> h...@zytor.com; gre...@linuxfoudation.org; x...@kernel.org;
> linux-kernel@vger.kernel.org;
Hi Mike
> Please keep the brief description of the function actually brief and move the
> detailed explanation after the parameters description.
Thanks for your advice.
> The allocation constraint is detected by the dump_header() callers, why not
> just use it here?
David suggest that
Hi Mike
> Please keep the brief description of the function actually brief and move the
> detailed explanation after the parameters description.
Thanks for your advice.
> The allocation constraint is detected by the dump_header() callers, why not
> just use it here?
David suggest that
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Sun, Jun 3, 2018 at 10:06 PM, Anson Huang wrote:
> Clock framework will enable those clocks registered
> with CLK_IS_CRITICAL flag, so no need to have
> clks_init_on array during clock initialization now.
>
> ARM clock is busy divider type which has the
> CLK_IS_CRITICAL flag set by default
On Wed 30 May 14:53 PDT 2018, Arnd Bergmann wrote:
> When CONFIG_GPIOLIB is disabled, we run into a build failure:
>
> drivers/pci/dwc/pcie-qcom.c: In function 'qcom_pcie_probe':
> drivers/pci/dwc/pcie-qcom.c:1223:16: error: implicit declaration of function
> 'devm_gpiod_get_optional'; did you
On Wed 30 May 14:53 PDT 2018, Arnd Bergmann wrote:
> When CONFIG_GPIOLIB is disabled, we run into a build failure:
>
> drivers/pci/dwc/pcie-qcom.c: In function 'qcom_pcie_probe':
> drivers/pci/dwc/pcie-qcom.c:1223:16: error: implicit declaration of function
> 'devm_gpiod_get_optional'; did you
misc bits and pieces not fitting into anything more specific.
That's probably it for tonight; more to follow tomorrow...
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
misc bits and pieces not fitting into anything more specific.
That's probably it for tonight; more to follow tomorrow...
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
Christoph's proc_create_... cleanups series.
The following changes since commit 67b8d5c7081221efa252e111cd52532ec6d4266f:
Linux 4.17-rc5 (2018-05-13 16:15:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git hch.procfs
for
Christoph's proc_create_... cleanups series.
The following changes since commit 67b8d5c7081221efa252e111cd52532ec6d4266f:
Linux 4.17-rc5 (2018-05-13 16:15:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git hch.procfs
for
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
IPG clock has no clock gate and its parent AHB
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
IPG clock has no clock gate and its parent AHB
Hi, Fabio
Anson Huang
Best Regards!
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Sunday, June 3, 2018 8:54 PM
> To: Anson Huang
> Cc: Shawn Guo ; Sascha Hauer
> ; Fabio Estevam ; Michael
> Turquette ; Stephen Boyd ;
> dl-linux-imx ; moderated
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
Signed-off-by: Anson Huang
---
This
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
Signed-off-by: Anson Huang
---
This
Hi, Fabio
Anson Huang
Best Regards!
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Sunday, June 3, 2018 8:54 PM
> To: Anson Huang
> Cc: Shawn Guo ; Sascha Hauer
> ; Fabio Estevam ; Michael
> Turquette ; Stephen Boyd ;
> dl-linux-imx ; moderated
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
Signed-off-by: Anson Huang
---
changes since
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
Signed-off-by: Anson Huang
---
changes since
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
IPG clock has no clock gate and its parent AHB
Clock framework will enable those clocks registered
with CLK_IS_CRITICAL flag, so no need to have
clks_init_on array during clock initialization now.
ARM clock is busy divider type which has the
CLK_IS_CRITICAL flag set by default when registered.
IPG clock has no clock gate and its parent AHB
Hi Andy,
On 2018/6/1 19:34, Andy Shevchenko wrote:
> On Thu, May 31, 2018 at 2:11 PM, Yisheng Xie wrote:
>> match_string() returns the index of an array for a matching string,
>> which can be used instead of open coded variant.
>
>> @@ -512,10 +512,9 @@ static unsigned long __init
Hi Andy,
On 2018/6/1 19:34, Andy Shevchenko wrote:
> On Thu, May 31, 2018 at 2:11 PM, Yisheng Xie wrote:
>> match_string() returns the index of an array for a matching string,
>> which can be used instead of open coded variant.
>
>> @@ -512,10 +512,9 @@ static unsigned long __init
More shrink_dcache_parent()-related stuff - killing the main
source of potentially contended calls of that on large subtrees.
The following changes since commit 4faa99965e027cc057c5145ce45fa772caa04e8d:
fix io_destroy()/aio_complete() race (2018-05-23 22:53:22 -0400)
are available in
More shrink_dcache_parent()-related stuff - killing the main
source of potentially contended calls of that on large subtrees.
The following changes since commit 4faa99965e027cc057c5145ce45fa772caa04e8d:
fix io_destroy()/aio_complete() race (2018-05-23 22:53:22 -0400)
are available in
That pile is the first part of dealing with livelocks, etc. around
shrink_dcache_parent().
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
That pile is the first part of dealing with livelocks, etc. around
shrink_dcache_parent().
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
On Fri 01 Jun 16:32 PDT 2018, Srinivas Kandagatla wrote:
> @@ -1380,11 +1380,13 @@ static void qcom_smd_edge_release(struct device *dev)
> {
> struct qcom_smd_channel *channel;
> struct qcom_smd_edge *edge = to_smd_edge(dev);
> + struct list_head *this, *tmp;
>
> -
On Fri 01 Jun 16:32 PDT 2018, Srinivas Kandagatla wrote:
> @@ -1380,11 +1380,13 @@ static void qcom_smd_edge_release(struct device *dev)
> {
> struct qcom_smd_channel *channel;
> struct qcom_smd_edge *edge = to_smd_edge(dev);
> + struct list_head *this, *tmp;
>
> -
1 - 100 of 342 matches
Mail list logo
