On Thu, 09 Aug 2018 18:30:53 +0100,
Stephen Boyd wrote:
>
> Quoting Marc Zyngier (2018-08-07 23:26:32)
> > On Tue, 07 Aug 2018 23:05:07 -0700
> > Stephen Boyd wrote:
> >
> > > Quoting Lina Iyer (2018-08-02 05:58:27)
> > > > On Thu, Aug 02 2018 at 01:27 -0600, Marc Zyngier wrote:
> > > > >
>
On Thu, 09 Aug 2018 18:30:53 +0100,
Stephen Boyd wrote:
>
> Quoting Marc Zyngier (2018-08-07 23:26:32)
> > On Tue, 07 Aug 2018 23:05:07 -0700
> > Stephen Boyd wrote:
> >
> > > Quoting Lina Iyer (2018-08-02 05:58:27)
> > > > On Thu, Aug 02 2018 at 01:27 -0600, Marc Zyngier wrote:
> > > > >
>
From: Rafael J. Wysocki
Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
with stopped tick) missed the case when the target residencies of
deep idle states of CPUs are above the tick boundary which may cause
the CPU to get stuck in a shallow idle state for a long time.
Say
From: Rafael J. Wysocki
Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
with stopped tick) missed the case when the target residencies of
deep idle states of CPUs are above the tick boundary which may cause
the CPU to get stuck in a shallow idle state for a long time.
Say
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
> [9.635329] x86/mm: Checking user space page tables
> [9.636271] [ cut here ]
> [9.637045] x86/mm: Found insecure W+X mapping at address
> (ptrval)/0xffc01000
> [9.638228] WARNING: CPU: 0
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
> [9.635329] x86/mm: Checking user space page tables
> [9.636271] [ cut here ]
> [9.637045] x86/mm: Found insecure W+X mapping at address
> (ptrval)/0xffc01000
> [9.638228] WARNING: CPU: 0
On Fri, Aug 10, 2018 at 7:53 AM, wrote:
> On Thu, Aug 09, 2018 at 11:31:46PM +0200, Rafael J . Wysocki wrote:
>
> [...]
>
>> > >> And I really would prefer to avoid restarting the tick here, because
>> > >> it is overhead and quite likely unnecessary.
>> > >
>> > > I understand the logic when
On Fri, Aug 10, 2018 at 7:53 AM, wrote:
> On Thu, Aug 09, 2018 at 11:31:46PM +0200, Rafael J . Wysocki wrote:
>
> [...]
>
>> > >> And I really would prefer to avoid restarting the tick here, because
>> > >> it is overhead and quite likely unnecessary.
>> > >
>> > > I understand the logic when
On Fri, Aug 10, 2018 at 9:13 AM, wrote:
> On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
>> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote:
[cut]
>> And that will cause the tick to be stopped unnecessarily in certain
>> situations, so why is this better?
>
> Let's see below
Hi Stefan,
I love your patch! Perhaps something to improve:
url:
https://github.com/0day-ci/linux/commits/Stefan-Popa/iio-accel-Add-adxl372-driver/20180807-050955
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
smatch warnings:
drivers/iio/accel/adxl372.c:704
On Fri, Aug 10, 2018 at 9:13 AM, wrote:
> On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
>> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote:
[cut]
>> And that will cause the tick to be stopped unnecessarily in certain
>> situations, so why is this better?
>
> Let's see below
Hi Stefan,
I love your patch! Perhaps something to improve:
url:
https://github.com/0day-ci/linux/commits/Stefan-Popa/iio-accel-Add-adxl372-driver/20180807-050955
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
smatch warnings:
drivers/iio/accel/adxl372.c:704
Use rtlwifi/phydm/phydm_reg.h instead of odm_reg.h and
remove the now unused odm_reg.h.
All defines from odm_reg.h are defined with the same values
in rtlwifi/phydm/phydm_reg.h.
Signed-off-by: Michael Straube
---
.../staging/rtl8188eu/include/odm_precomp.h | 2 +-
Use is_multicast_ether_addr instead of custom IS_MCAST in
core/rtw_security.c. In all uses the address array is properly
aligned.
Signed-off-by: Michael Straube
---
v2: checked that in all uses of is_multicast_ether_addr
the address array/memory is properly aligned and
updated the commit
Use is_multicast_ether_addr instead of custom IS_MCAST in
core/rtw_security.c. In all uses the address array is properly
aligned.
Signed-off-by: Michael Straube
---
v2: checked that in all uses of is_multicast_ether_addr
the address array/memory is properly aligned and
updated the commit
Use rtlwifi/phydm/phydm_reg.h instead of odm_reg.h and
remove the now unused odm_reg.h.
All defines from odm_reg.h are defined with the same values
in rtlwifi/phydm/phydm_reg.h.
Signed-off-by: Michael Straube
---
.../staging/rtl8188eu/include/odm_precomp.h | 2 +-
Use is_multicast_ether_addr instead of custom IS_MCAST in
core/rtw_xmit.c. In all uses the address array is properly
aligned.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_xmit.c | 35 +++
1 file changed, 16 insertions(+), 19 deletions(-)
diff --git
Use is_multicast_ether_addr instead of custom IS_MCAST in
core/rtw_xmit.c. In all uses the address array is properly
aligned.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_xmit.c | 35 +++
1 file changed, 16 insertions(+), 19 deletions(-)
diff --git
Use is_multicast_ether_addr instead of custom IS_MCAST in
core/rtw_recv.c. In all uses the address array/memory is
properly aligned.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_recv.c | 35 ---
1 file changed, 18 insertions(+), 17 deletions(-)
diff
Remove the now unused IS_MCAST.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/include/wifi.h | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/staging/rtl8188eu/include/wifi.h
b/drivers/staging/rtl8188eu/include/wifi.h
index 4a56e54e38f6..0a952edf8a81 100644
---
Use is_multicast_ether_addr instead of custom IS_MCAST in
core/rtw_recv.c. In all uses the address array/memory is
properly aligned.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_recv.c | 35 ---
1 file changed, 18 insertions(+), 17 deletions(-)
diff
Remove the now unused IS_MCAST.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/include/wifi.h | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/staging/rtl8188eu/include/wifi.h
b/drivers/staging/rtl8188eu/include/wifi.h
index 4a56e54e38f6..0a952edf8a81 100644
---
On Fri, Aug 10, 2018 at 8:19 AM, wrote:
> On Thu, Aug 09, 2018 at 07:08:34PM +0200, Rafael J . Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> If the tick has been stopped already, but the governor has not asked to
>> stop it (which it can do sometimes), the idle loop should invoke
>>
On Fri, Aug 10, 2018 at 8:19 AM, wrote:
> On Thu, Aug 09, 2018 at 07:08:34PM +0200, Rafael J . Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> If the tick has been stopped already, but the governor has not asked to
>> stop it (which it can do sometimes), the idle loop should invoke
>>
On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote:
> > The criteria for keeping tick running is the prediction duration is less
> > than TICK_USEC,
>
> Yes, because if the predicted idle duration is less than the tick
> period,
On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote:
> > The criteria for keeping tick running is the prediction duration is less
> > than TICK_USEC,
>
> Yes, because if the predicted idle duration is less than the tick
> period,
Hi Dou,
On Fri, 10 Aug 2018 at 04:35, Dou Liyang wrote:
>
> When compiling kernel with SMP disabled, the build warns with:
>
> kernel/sched/core.c: In function ‘update_rq_clock_task’:
> kernel/sched/core.c:139:17: warning: unused variable ‘irq_delta’
> [-Wunused-variable]
> s64 steal = 0,
Hi Dou,
On Fri, 10 Aug 2018 at 04:35, Dou Liyang wrote:
>
> When compiling kernel with SMP disabled, the build warns with:
>
> kernel/sched/core.c: In function ‘update_rq_clock_task’:
> kernel/sched/core.c:139:17: warning: unused variable ‘irq_delta’
> [-Wunused-variable]
> s64 steal = 0,
On Fri, Aug 10, 2018 at 12:30 AM, wrote:
> On 2018-08-06 01:53, Rafael J. Wysocki wrote:
>>
>> On Fri, Aug 3, 2018 at 12:20 AM, Sodagudi Prasad
>> wrote:
From: RAFAEL J. WYSOCKI
Date: Wed, Aug 1, 2018 at 2:21 PM
Subject: Re: [PATCH] dd: Invoke one probe retry cycle after
On Fri, Aug 10, 2018 at 12:30 AM, wrote:
> On 2018-08-06 01:53, Rafael J. Wysocki wrote:
>>
>> On Fri, Aug 3, 2018 at 12:20 AM, Sodagudi Prasad
>> wrote:
From: RAFAEL J. WYSOCKI
Date: Wed, Aug 1, 2018 at 2:21 PM
Subject: Re: [PATCH] dd: Invoke one probe retry cycle after
On Thu, Aug 09, 2018 at 09:34:16AM -0500, Tom Zanussi wrote:
> From: Tom Zanussi
>
> Add support for hist:handlerXXX($var).snapshot(), which will take a
> snapshot of the current trace buffer whenever handlerXXX is hit.
>
> As a first user, this also adds snapshot() action support for the
>
On Thu 09-08-18 13:10:10, David Rientjes wrote:
> On Wed, 8 Aug 2018, Michal Hocko wrote:
>
> > > > > In a cgroup-aware oom killer world, yes, we need the ability to
> > > > > specify
> > > > > that the usage of the entire subtree should be compared as a single
> > > > > entity with other
On Thu, Aug 09, 2018 at 09:34:16AM -0500, Tom Zanussi wrote:
> From: Tom Zanussi
>
> Add support for hist:handlerXXX($var).snapshot(), which will take a
> snapshot of the current trace buffer whenever handlerXXX is hit.
>
> As a first user, this also adds snapshot() action support for the
>
On Thu 09-08-18 13:10:10, David Rientjes wrote:
> On Wed, 8 Aug 2018, Michal Hocko wrote:
>
> > > > > In a cgroup-aware oom killer world, yes, we need the ability to
> > > > > specify
> > > > > that the usage of the entire subtree should be compared as a single
> > > > > entity with other
On Thu, Aug 09, 2018 at 09:34:14AM -0500, Tom Zanussi wrote:
> From: Tom Zanussi
>
> Currently, tracing snapshots are context-free - they capture the ring
> buffer contents at the time the tracing_snapshot() function was
> invoked, and nothing else. Additionally, they're always taken
>
On Thu, Aug 09, 2018 at 09:34:14AM -0500, Tom Zanussi wrote:
> From: Tom Zanussi
>
> Currently, tracing snapshots are context-free - they capture the ring
> buffer contents at the time the tracing_snapshot() function was
> invoked, and nothing else. Additionally, they're always taken
>
Hi Tom,
On Thu, Aug 09, 2018 at 09:34:11AM -0500, Tom Zanussi wrote:
> From: Tom Zanussi
>
> The hist trigger action code currently implements two essentially
> hard-coded pairs of 'actions' - onmax(), which tracks a variable and
> saves some event fields when a max is hit, and onmatch(), which
Hi Tom,
On Thu, Aug 09, 2018 at 09:34:11AM -0500, Tom Zanussi wrote:
> From: Tom Zanussi
>
> The hist trigger action code currently implements two essentially
> hard-coded pairs of 'actions' - onmax(), which tracks a variable and
> saves some event fields when a max is hit, and onmatch(), which
On Fri, Aug 10, 2018 at 11:12 AM, Andrew Morton
wrote:
> On Thu, 9 Aug 2018 12:54:09 +1000 Rashmica Gupta
> wrote:
>
>> When hot-removing memory release_mem_region_adjustable() splits
>> iomem resources if they are not the exact size of the memory being
>> hot-deleted. Adding this memory back
On Fri, Aug 10, 2018 at 11:12 AM, Andrew Morton
wrote:
> On Thu, 9 Aug 2018 12:54:09 +1000 Rashmica Gupta
> wrote:
>
>> When hot-removing memory release_mem_region_adjustable() splits
>> iomem resources if they are not the exact size of the memory being
>> hot-deleted. Adding this memory back
On 2018년 08월 08일 19:06, Seung-Woo Kim wrote:
> On 2018년 07월 05일 09:52, Al Viro wrote:
>> On Mon, Jul 02, 2018 at 10:01:25PM -0700, Linus Torvalds wrote:
>>> On Mon, Jul 2, 2018 at 9:43 PM Seung-Woo Kim wrote:
I think the commit itself is required. Simple, but not reliable,
2018-08-09 9:53 GMT+02:00 Neil Armstrong :
> On 08/08/2018 10:41, Jerome Brunet wrote:
>> On Wed, 2018-08-08 at 00:00 +0200, Maxime Jourdan wrote:
>>> Wrap the canvas node in a syscon node.
>>>
>>> Signed-off-by: Maxime Jourdan
>>> ---
>>> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 17
On 2018년 08월 08일 19:06, Seung-Woo Kim wrote:
> On 2018년 07월 05일 09:52, Al Viro wrote:
>> On Mon, Jul 02, 2018 at 10:01:25PM -0700, Linus Torvalds wrote:
>>> On Mon, Jul 2, 2018 at 9:43 PM Seung-Woo Kim wrote:
I think the commit itself is required. Simple, but not reliable,
2018-08-09 9:53 GMT+02:00 Neil Armstrong :
> On 08/08/2018 10:41, Jerome Brunet wrote:
>> On Wed, 2018-08-08 at 00:00 +0200, Maxime Jourdan wrote:
>>> Wrap the canvas node in a syscon node.
>>>
>>> Signed-off-by: Maxime Jourdan
>>> ---
>>> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 17
2018-08-08 17:10 GMT+02:00 Neil Armstrong :
> On 08/08/2018 09:45, Jerome Brunet wrote:
>> On Wed, 2018-08-08 at 00:00 +0200, Maxime Jourdan wrote:
>>> Amlogic SoCs have a repository of 256 canvas which they use to
>>> describe pixel buffers.
>>>
>>> They contain metadata like width, height, block
2018-08-08 17:10 GMT+02:00 Neil Armstrong :
> On 08/08/2018 09:45, Jerome Brunet wrote:
>> On Wed, 2018-08-08 at 00:00 +0200, Maxime Jourdan wrote:
>>> Amlogic SoCs have a repository of 256 canvas which they use to
>>> describe pixel buffers.
>>>
>>> They contain metadata like width, height, block
Hi Matthew,
After merging the ida tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/target/iscsi/iscsi_target_login.c: In function
'iscsi_login_zero_tsih_s1':
drivers/target/iscsi/iscsi_target_login.c:376:16: error: 'sess_idr_lock'
undeclared (first use in this
Hi Matthew,
After merging the ida tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/target/iscsi/iscsi_target_login.c: In function
'iscsi_login_zero_tsih_s1':
drivers/target/iscsi/iscsi_target_login.c:376:16: error: 'sess_idr_lock'
undeclared (first use in this
On Thu, Aug 09, 2018 at 07:08:34PM +0200, Rafael J . Wysocki wrote:
> From: Rafael J. Wysocki
>
> If the tick has been stopped already, but the governor has not asked to
> stop it (which it can do sometimes), the idle loop should invoke
> tick_nohz_idle_stop_tick(), to let tick_nohz_stop_tick()
On Thu, Aug 09, 2018 at 07:08:34PM +0200, Rafael J . Wysocki wrote:
> From: Rafael J. Wysocki
>
> If the tick has been stopped already, but the governor has not asked to
> stop it (which it can do sometimes), the idle loop should invoke
> tick_nohz_idle_stop_tick(), to let tick_nohz_stop_tick()
On Thu, Aug 09, 2018 at 08:40:06PM -0700, John Joseph wrote:
> Acked-by: John Joseph
Why are you acking something you supposidly already signed-off on?
> On Thu, Aug 9, 2018 at 8:20 PM, Todd Poynor wrote:
> > From: Todd Poynor
> >
> > Todd Poynor takes over for John Joseph.
> >
> >
On Thu, Aug 09, 2018 at 08:40:06PM -0700, John Joseph wrote:
> Acked-by: John Joseph
Why are you acking something you supposidly already signed-off on?
> On Thu, Aug 9, 2018 at 8:20 PM, Todd Poynor wrote:
> > From: Todd Poynor
> >
> > Todd Poynor takes over for John Joseph.
> >
> >
Hi Abel,
On Thu, Aug 09, 2018 at 05:45:37PM +0300, Abel Vesa wrote:
> This is basically just a resend of the following patchset:
>
> https://www.spinics.net/lists/linux-clk/msg23141.html
>
> I've just updated the patchset and implemented Shawn's
> and Aisheng's comments.
>
> I hope I haven't
Hi Abel,
On Thu, Aug 09, 2018 at 05:45:37PM +0300, Abel Vesa wrote:
> This is basically just a resend of the following patchset:
>
> https://www.spinics.net/lists/linux-clk/msg23141.html
>
> I've just updated the patchset and implemented Shawn's
> and Aisheng's comments.
>
> I hope I haven't
801 - 854 of 854 matches
Mail list logo
