On Thu, Sep 8, 2016 at 7:27 PM, Rob Herring wrote:
> On Thu, Sep 8, 2016 at 7:39 PM, John Stultz wrote:
>> On Thu, Sep 8, 2016 at 5:33 PM, Rob Herring wrote:
>>> If you can figure out how to change the command line, then you can
On Thu, Sep 8, 2016 at 7:27 PM, Rob Herring wrote:
> On Thu, Sep 8, 2016 at 7:39 PM, John Stultz wrote:
>> On Thu, Sep 8, 2016 at 5:33 PM, Rob Herring wrote:
>>> If you can figure out how to change the command line, then you can
>>> just change the dtb. At least for how Android boot works,
Moving data to text is a good thing.
Mark the regulator_info structs as const and change the pointers to const.
$ size drivers/regulator/*.o*
textdata bss dec hex filename
7455 100 075551d83 drivers/regulator/da9052-regulator.o.new
21115392 0
Moving data to text is a good thing.
Mark the regulator_info structs as const and change the pointers to const.
$ size drivers/regulator/*.o*
textdata bss dec hex filename
7455 100 075551d83 drivers/regulator/da9052-regulator.o.new
21115392 0
On Tue, Sep 06, 2016 at 10:48:39AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 06, 2016 at 02:05:17PM +0900, Byungchul Park wrote:
> > From 295895be8befbab040d6054bb8186c03daabcedd Mon Sep 17 00:00:00 2001
> > From: Byungchul Park
> > Date: Tue, 6 Sep 2016 12:22:26 +0900
>
On Tue, Sep 06, 2016 at 10:48:39AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 06, 2016 at 02:05:17PM +0900, Byungchul Park wrote:
> > From 295895be8befbab040d6054bb8186c03daabcedd Mon Sep 17 00:00:00 2001
> > From: Byungchul Park
> > Date: Tue, 6 Sep 2016 12:22:26 +0900
> > Subject: [PATCH]
On Thu, Sep 8, 2016 at 2:05 PM, Frank Rowand wrote:
> On 09/08/16 06:38, Rob Herring wrote:
>> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote:
>>> * Frank Rowand [160831 13:51]:
On 08/29/16 15:35, Tony Lindgren wrote:
On Thu, Sep 8, 2016 at 2:05 PM, Frank Rowand wrote:
> On 09/08/16 06:38, Rob Herring wrote:
>> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote:
>>> * Frank Rowand [160831 13:51]:
On 08/29/16 15:35, Tony Lindgren wrote:
> if (of_device_is_incomplete(pdev->dev.of_node, status))
Hi,
The idea of my patch is a little bit different. It targets to associate the
branch
coverage percentage and branch mispredict rate with the source code then user
can see them directly in perf annotate source code / assembly view.
The screenshot to show the branch%.
Hi,
The idea of my patch is a little bit different. It targets to associate the
branch
coverage percentage and branch mispredict rate with the source code then user
can see them directly in perf annotate source code / assembly view.
The screenshot to show the branch%.
Hi xiaolong,
OK, I found it :
https://github.com/0day-ci/linux/commit/3d26b7622f3bab689696900ffd33c6dd7849d7c2
but this patch have already updated later. the logic is on when
CONFIG_PREEMPT_NONE=y
the latest patch review is here:
https://lkml.org/lkml/2016/9/7/819
thanks,
Cheng
on
Hi xiaolong,
OK, I found it :
https://github.com/0day-ci/linux/commit/3d26b7622f3bab689696900ffd33c6dd7849d7c2
but this patch have already updated later. the logic is on when
CONFIG_PREEMPT_NONE=y
the latest patch review is here:
https://lkml.org/lkml/2016/9/7/819
thanks,
Cheng
on
On Thu, Sep 8, 2016 at 1:32 PM, Suman Anna wrote:
> Hi Rob,
>
> On 09/08/2016 11:50 AM, Rob Herring wrote:
>> On Fri, Sep 02, 2016 at 04:45:45PM -0500, Suman Anna wrote:
>>> On 08/12/2016 05:42 PM, Bjorn Andersson wrote:
On Fri 12 Aug 11:34 PDT 2016, Rob Herring wrote:
On Thu, Sep 8, 2016 at 1:32 PM, Suman Anna wrote:
> Hi Rob,
>
> On 09/08/2016 11:50 AM, Rob Herring wrote:
>> On Fri, Sep 02, 2016 at 04:45:45PM -0500, Suman Anna wrote:
>>> On 08/12/2016 05:42 PM, Bjorn Andersson wrote:
On Fri 12 Aug 11:34 PDT 2016, Rob Herring wrote:
> On Wed, Aug
Hi, cheng hao,
On 09/09, chengchao wrote:
>Hi, xiaolong
>
> where can I find the commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2?
This is the commit by 0Day bot for your original email patch sent on Sep 05
where
both CONFIG_PREEMPT_NONE and CONFIG_PREEMPT_VOLUNTARY will turn the
logic on.
Hi, cheng hao,
On 09/09, chengchao wrote:
>Hi, xiaolong
>
> where can I find the commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2?
This is the commit by 0Day bot for your original email patch sent on Sep 05
where
both CONFIG_PREEMPT_NONE and CONFIG_PREEMPT_VOLUNTARY will turn the
logic on.
On Thu, Sep 8, 2016 at 7:39 PM, John Stultz wrote:
> On Thu, Sep 8, 2016 at 5:33 PM, Rob Herring wrote:
>> On Thu, Sep 8, 2016 at 4:15 PM, Dmitry Shmidt wrote:
>>> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand
On Thu, Sep 8, 2016 at 7:39 PM, John Stultz wrote:
> On Thu, Sep 8, 2016 at 5:33 PM, Rob Herring wrote:
>> On Thu, Sep 8, 2016 at 4:15 PM, Dmitry Shmidt wrote:
>>> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
What problem(s) are you trying to solve with this?
>>>
>>> Currently the
Moved the instance boundary check to the start of the pcal9555a
platform init code. This will prevent unnecessary initialization
on instance boundary error.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
Moved the instance boundary check to the start of the pcal9555a
platform init code. This will prevent unnecessary initialization
on instance boundary error.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
arch/x86/platform/intel-mid/device_libs/platform_pcal9555a.c | 12 ++--
1 file
According to the intel_mid_sfi_get_pdata() definition,
get_platform_data() should return NULL on no platform
data scenario and return ERR_PTR on platform data
initialization failures. But current device platform
initialization code does not follow this requirement.
This patch fixes the return
Added valid error/warning messages to platform data
initalization failures in SFI device libs code.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
.../intel-mid/device_libs/platform_emc1403.c| 18 ++
According to the intel_mid_sfi_get_pdata() definition,
get_platform_data() should return NULL on no platform
data scenario and return ERR_PTR on platform data
initialization failures. But current device platform
initialization code does not follow this requirement.
This patch fixes the return
Added valid error/warning messages to platform data
initalization failures in SFI device libs code.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
.../intel-mid/device_libs/platform_emc1403.c| 18 ++
.../platform/intel-mid/device_libs/platform_ipc.c | 5 -
According to the Smart Battery Data Specification, the use
of ManufacturerAcess (register 0x0) is implementation-defined.
It appears that some batteries use writes to this register
in order to implement certain functionality, but others may
simply NAK all writes to it. As a result, write failures
According to the Smart Battery Data Specification, the use
of ManufacturerAcess (register 0x0) is implementation-defined.
It appears that some batteries use writes to this register
in order to implement certain functionality, but others may
simply NAK all writes to it. As a result, write failures
On 2016/9/8 19:01, Will Deacon wrote:
> On Thu, Sep 01, 2016 at 02:54:51PM +0800, Zhen Lei wrote:
>> v7 -> v8:
>> Updated patches according to Will Deacon's review comments, thanks.
>>
>> The changed patches is: 3, 5, 8, 9, 10, 11, 12, 13, 15
>> Patch 3 requires an ack from Rob Herring.
>> Patch
On 2016/9/8 19:01, Will Deacon wrote:
> On Thu, Sep 01, 2016 at 02:54:51PM +0800, Zhen Lei wrote:
>> v7 -> v8:
>> Updated patches according to Will Deacon's review comments, thanks.
>>
>> The changed patches is: 3, 5, 8, 9, 10, 11, 12, 13, 15
>> Patch 3 requires an ack from Rob Herring.
>> Patch
Hi Felipe,
On 8 September 2016 at 20:00, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> When we change the USB function with configfs dynamically, we possibly met
>> this
>> situation: one core is doing the control transfer, another core is
Hi Felipe,
On 8 September 2016 at 20:00, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> When we change the USB function with configfs dynamically, we possibly met
>> this
>> situation: one core is doing the control transfer, another core is trying to
>> unregister the USB gadget from
Hi, xiaolong
where can I find the commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2?
config-4.8.0-rc5-1-g3d26b76:
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
the patch ("sched/core: simpler function for sched_exec migration") only is
on if
Hi, xiaolong
where can I find the commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2?
config-4.8.0-rc5-1-g3d26b76:
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
the patch ("sched/core: simpler function for sched_exec migration") only is
on if
On Thu, Sep 08, 2016 at 03:59:19PM +0300, Grygorii Strashko wrote:
> On 09/08/2016 03:28 PM, Peter Chen wrote:
> > On Thu, Sep 08, 2016 at 12:17:21PM +0200, Arnd Bergmann wrote:
> >> On Thursday, September 8, 2016 12:43:06 PM CEST Felipe Balbi wrote:
> >>> Arnd Bergmann writes:
>
On Thu, Sep 08, 2016 at 03:59:19PM +0300, Grygorii Strashko wrote:
> On 09/08/2016 03:28 PM, Peter Chen wrote:
> > On Thu, Sep 08, 2016 at 12:17:21PM +0200, Arnd Bergmann wrote:
> >> On Thursday, September 8, 2016 12:43:06 PM CEST Felipe Balbi wrote:
> >>> Arnd Bergmann writes:
> On
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
cheng-chao/sched-core-simpler-function-for-sched_exec-migration/20160905-142452
commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2 ("sched/core: simpler function
for sched_exec migration")
in testcase: trinity
with following
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
cheng-chao/sched-core-simpler-function-for-sched_exec-migration/20160905-142452
commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2 ("sched/core: simpler function
for sched_exec migration")
in testcase: trinity
with following
On Thu, Sep 01 2016, Ian Kent wrote:
> Somewhere along the way the autofs expire operation has changed to
> hold a spin lock over expired dentry selection. The autofs indirect
> mount expired dentry selection is complicated and quite lengthy so
> it isn't appropriate to hold a spin lock over the
On Thu, Sep 01 2016, Ian Kent wrote:
> Somewhere along the way the autofs expire operation has changed to
> hold a spin lock over expired dentry selection. The autofs indirect
> mount expired dentry selection is complicated and quite lengthy so
> it isn't appropriate to hold a spin lock over the
On Thu, Sep 08, 2016 at 02:52:29PM +0200, Arnd Bergmann wrote:
> On Thursday, September 8, 2016 8:28:10 PM CEST Peter Chen wrote:
> > On Thu, Sep 08, 2016 at 12:17:21PM +0200, Arnd Bergmann wrote:
> > > On Thursday, September 8, 2016 12:43:06 PM CEST Felipe Balbi wrote:
> > > > Arnd Bergmann
On Thu, Sep 08, 2016 at 02:52:29PM +0200, Arnd Bergmann wrote:
> On Thursday, September 8, 2016 8:28:10 PM CEST Peter Chen wrote:
> > On Thu, Sep 08, 2016 at 12:17:21PM +0200, Arnd Bergmann wrote:
> > > On Thursday, September 8, 2016 12:43:06 PM CEST Felipe Balbi wrote:
> > > > Arnd Bergmann
These GPU drivers only depend on the RESET_CONTROLLER config
option to fix build issues that existed when there weren't stub
reset APIs for reset controller consumers. Given that these
drivers aren't providing any reset controllers themselves, they
don't actually depend on the API to build (just
These GPU drivers only depend on the RESET_CONTROLLER config
option to fix build issues that existed when there weren't stub
reset APIs for reset controller consumers. Given that these
drivers aren't providing any reset controllers themselves, they
don't actually depend on the API to build (just
Commit 4d9424669946 ("mm: convert p[te|md]_mknonnuma and remaining
page table manipulations") changed NUMA balancing from _PAGE_NUMA
to using PROT_NONE, and was quickly found to introduce a regression
with NUMA grouping.
It was followed up by these changesets:
53da3bc2ba9e ("mm: fix up numa
Commit 4d9424669946 ("mm: convert p[te|md]_mknonnuma and remaining
page table manipulations") changed NUMA balancing from _PAGE_NUMA
to using PROT_NONE, and was quickly found to introduce a regression
with NUMA grouping.
It was followed up by these changesets:
53da3bc2ba9e ("mm: fix up numa
On Wed, 2016-09-07 at 18:10 +0100, Colin King wrote:
> From: Colin Ian King
>
> pdev is being null checked, however, prior to that it is being
> dereferenced by platform_get_drvdata. Move the assignments of
> vpu and run to after the pdev null check to avoid a
On Wed, 2016-09-07 at 18:10 +0100, Colin King wrote:
> From: Colin Ian King
>
> pdev is being null checked, however, prior to that it is being
> dereferenced by platform_get_drvdata. Move the assignments of
> vpu and run to after the pdev null check to avoid a potential
> null pointer
On Fri, Sep 9, 2016 at 4:11 AM, Luis R. Rodriguez wrote:
> On Thu, Sep 08, 2016 at 11:37:54PM +0800, Ming Lei wrote:
>> On Wed, Sep 7, 2016 at 4:45 PM, Daniel Wagner wrote:
>> > From: Daniel Wagner
>> >
>> > When we load the
On Fri, Sep 9, 2016 at 4:11 AM, Luis R. Rodriguez wrote:
> On Thu, Sep 08, 2016 at 11:37:54PM +0800, Ming Lei wrote:
>> On Wed, Sep 7, 2016 at 4:45 PM, Daniel Wagner wrote:
>> > From: Daniel Wagner
>> >
>> > When we load the firmware directly we don't need to take the umh
>> > lock.
>>
>> I am
We get a few warnings when building kernel with W=1:
drivers/net/ethernet/qlogic/qed/qed_l2.c:112:5: warning: no previous prototype
for 'qed_sp_vport_start' [-Wmissing-prototypes]
drivers/net/ethernet/qlogic/qed/qed_sriov.c:110:6: warning: no previous
prototype for 'qed_iov_is_valid_vfid'
We get a few warnings when building kernel with W=1:
drivers/net/ethernet/qlogic/qed/qed_l2.c:112:5: warning: no previous prototype
for 'qed_sp_vport_start' [-Wmissing-prototypes]
drivers/net/ethernet/qlogic/qed/qed_sriov.c:110:6: warning: no previous
prototype for 'qed_iov_is_valid_vfid'
On Thu, 2016-09-08 at 17:12 -0400, Josef Bacik wrote:
> In preparation for some future changes, change a few of the state bools over
> to
> normal bits to set/clear properly.
[]
> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
[]
> @@ -41,8 +41,12 @@
>
> #include
>
> +#define
On Thu, 2016-09-08 at 17:12 -0400, Josef Bacik wrote:
> In preparation for some future changes, change a few of the state bools over
> to
> normal bits to set/clear properly.
[]
> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
[]
> @@ -41,8 +41,12 @@
>
> #include
>
> +#define
On Thu, 8 Sep 2016 12:50:43 -0400
Vivien Didelot wrote:
> If /sbin/bridge-stp is available on the system, bridge tries to execute
> it instead of the kernel implementation when starting/stopping STP.
>
> If anything goes wrong with /sbin/bridge-stp, bridge
On Thu, 8 Sep 2016 12:50:43 -0400
Vivien Didelot wrote:
> If /sbin/bridge-stp is available on the system, bridge tries to execute
> it instead of the kernel implementation when starting/stopping STP.
>
> If anything goes wrong with /sbin/bridge-stp, bridge silently falls back
> to kernel STP,
On Tue, 06 Sep 2016 08:08:59 -0700
Jay Vosburgh wrote:
> Kaur, Jasminder wrote:
>
> >From: "Kaur, Jasminder"
> >
> >If a bond is in use such as with IP address configured, removing it
> >can result in application
On Tue, 06 Sep 2016 08:08:59 -0700
Jay Vosburgh wrote:
> Kaur, Jasminder wrote:
>
> >From: "Kaur, Jasminder"
> >
> >If a bond is in use such as with IP address configured, removing it
> >can result in application disruptions. If bond is used for cluster
> >communication or network file system
On Thu, Sep 08, 2016 at 08:58:48AM -0400, Chris Mason wrote:
> On 09/08/2016 07:50 AM, Christian Borntraeger wrote:
> > On 09/08/2016 01:48 PM, Christian Borntraeger wrote:
> >> Chris,
> >>
> >> with 4.8-rc3 I get the following on an s390 box:
> >
> > Sorry for the noise, just saw the fix
On Thu, Sep 08, 2016 at 08:58:48AM -0400, Chris Mason wrote:
> On 09/08/2016 07:50 AM, Christian Borntraeger wrote:
> > On 09/08/2016 01:48 PM, Christian Borntraeger wrote:
> >> Chris,
> >>
> >> with 4.8-rc3 I get the following on an s390 box:
> >
> > Sorry for the noise, just saw the fix
On 09/08, Jens Axboe wrote:
>On 09/07/2016 08:04 PM, Ye Xiaolong wrote:
>>On 09/08, Fengguang Wu wrote:
>>>Hi Jens and Tejun,
>>>
The command line was in the original email:
$ qemu-system-x86_64 -enable-kvm -cpu Westmere -m 512M
And agree, in general it'd be nice if there was
On 09/08, Jens Axboe wrote:
>On 09/07/2016 08:04 PM, Ye Xiaolong wrote:
>>On 09/08, Fengguang Wu wrote:
>>>Hi Jens and Tejun,
>>>
The command line was in the original email:
$ qemu-system-x86_64 -enable-kvm -cpu Westmere -m 512M
And agree, in general it'd be nice if there was
On Thu, Sep 08, 2016 at 02:13:28PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-09-07 19:06:45)
> > On Thu, Sep 8, 2016 at 5:34 AM, Stephen Boyd
> > wrote:
> > > The state of USB ChipIdea support on Qualcomm's platforms is not great.
> > > The DT description of
On Thu, Sep 08, 2016 at 02:13:28PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-09-07 19:06:45)
> > On Thu, Sep 8, 2016 at 5:34 AM, Stephen Boyd
> > wrote:
> > > The state of USB ChipIdea support on Qualcomm's platforms is not great.
> > > The DT description of these devices requires up
On Tuesday 06 September 2016 02:40 PM, Peter Zijlstra wrote:
On Tue, Sep 06, 2016 at 09:55:43AM +0530, Madhavan Srinivasan wrote:
On Thursday 01 September 2016 12:56 PM, Peter Zijlstra wrote:
On Mon, Aug 29, 2016 at 02:30:46AM +0530, Madhavan Srinivasan wrote:
It's a perennial request from
On Tuesday 06 September 2016 02:40 PM, Peter Zijlstra wrote:
On Tue, Sep 06, 2016 at 09:55:43AM +0530, Madhavan Srinivasan wrote:
On Thursday 01 September 2016 12:56 PM, Peter Zijlstra wrote:
On Mon, Aug 29, 2016 at 02:30:46AM +0530, Madhavan Srinivasan wrote:
It's a perennial request from
Discrepancy between cpu_online_mask and cpuset's effective CPU masks on
cpuset hierarchy is inevitable since cpuset defers updating of
effective CPU masks with workqueue while nothing prevents system from
doing CPU hotplug. For that reason guarantee_online_cpus() walks up
the cpuset hierarchy
Discrepancy between cpu_online_mask and cpuset's effective CPU masks on
cpuset hierarchy is inevitable since cpuset defers updating of
effective CPU masks with workqueue while nothing prevents system from
doing CPU hotplug. For that reason guarantee_online_cpus() walks up
the cpuset hierarchy
This patch includes below modifications:
1. change my maintainership from reviewer to maintainer.
2. remove maintainership of Changman Lee since he is not active about
one and a half year.
3. change website of f2fs from wiki to kernel one.
Signed-off-by: Chao Yu
---
v2:
On Thu, Sep 8, 2016 at 5:33 PM, Rob Herring wrote:
> On Thu, Sep 8, 2016 at 4:15 PM, Dmitry Shmidt wrote:
>> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>>> What problem(s) are you trying to solve with this?
>>
>>
This patch includes below modifications:
1. change my maintainership from reviewer to maintainer.
2. remove maintainership of Changman Lee since he is not active about
one and a half year.
3. change website of f2fs from wiki to kernel one.
Signed-off-by: Chao Yu
---
v2: gather more modification
On Thu, Sep 8, 2016 at 5:33 PM, Rob Herring wrote:
> On Thu, Sep 8, 2016 at 4:15 PM, Dmitry Shmidt wrote:
>> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>>> What problem(s) are you trying to solve with this?
>>
>> Currently the Linux kernel doesn't provide a way for boot time
>>
On Thu, Sep 08, 2016 at 07:56:28PM -0400, Nicolas Pitre wrote:
> On Thu, 8 Sep 2016, Josh Triplett wrote:
>
> > On Thu, Sep 08, 2016 at 02:19:24PM -0700, John Stultz wrote:
> > > On Thu, Sep 8, 2016 at 2:05 PM, Nicolas Pitre wrote:
> > > > Small embedded systems typically don't
On Thu, Sep 08, 2016 at 07:56:28PM -0400, Nicolas Pitre wrote:
> On Thu, 8 Sep 2016, Josh Triplett wrote:
>
> > On Thu, Sep 08, 2016 at 02:19:24PM -0700, John Stultz wrote:
> > > On Thu, Sep 8, 2016 at 2:05 PM, Nicolas Pitre wrote:
> > > > Small embedded systems typically don't need them. This
On Thu, Sep 8, 2016 at 4:15 PM, Dmitry Shmidt wrote:
> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>> On 09/08/16 13:35, dimitr...@google.com wrote:
>>> From e14eb45fa5a93c1bff8a6dfe7b6756e4ad72c579 Mon Sep 17 00:00:00 2001
>>> From: Dmitry
On Thu, Sep 8, 2016 at 4:15 PM, Dmitry Shmidt wrote:
> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>> On 09/08/16 13:35, dimitr...@google.com wrote:
>>> From e14eb45fa5a93c1bff8a6dfe7b6756e4ad72c579 Mon Sep 17 00:00:00 2001
>>> From: Dmitry Shmidt
>>> Date: Wed, 24 Aug 2016 13:25:52
On 08/16, Krzysztof Kozlowski wrote:
> Hi,
>
> RFC, please, do not apply, maybe except patch #1 which is harmless.
>
>
> Introduction
>
> The patchset brings new entity: clock controller representing a hardware
> block. The clock controller comes with its own prepare lock which
>
On 08/16, Krzysztof Kozlowski wrote:
> Hi,
>
> RFC, please, do not apply, maybe except patch #1 which is harmless.
>
>
> Introduction
>
> The patchset brings new entity: clock controller representing a hardware
> block. The clock controller comes with its own prepare lock which
>
Check for vb2_ops structures that are only stored in the ops field of a
vb2_queue structure. That field is declared const, so vb2_ops structures
that have this property can be declared as const also.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@r
Check for vb2_ops structures that are only stored in the ops field of a
vb2_queue structure. That field is declared const, so vb2_ops structures
that have this property can be declared as const also.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@r
Check for vb2_ops structures that are only stored in the ops field of a
vb2_queue structure. That field is declared const, so vb2_ops structures
that have this property can be declared as const also.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@r
On Thu, Sep 8, 2016 at 5:12 PM, Kees Cook wrote:
> On Mon, Aug 22, 2016 at 3:48 PM, John Stultz wrote:
>> This patch reserves some memory in the DTS and sets up a
>> pstore device tree node to enable pstore support on HiKey.
>>
>> Cc: Kees Cook
Check for vb2_ops structures that are only stored in the ops field of a
vb2_queue structure. That field is declared const, so vb2_ops structures
that have this property can be declared as const also.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@r
On Thu, Sep 8, 2016 at 5:12 PM, Kees Cook wrote:
> On Mon, Aug 22, 2016 at 3:48 PM, John Stultz wrote:
>> This patch reserves some memory in the DTS and sets up a
>> pstore device tree node to enable pstore support on HiKey.
>>
>> Cc: Kees Cook
>> Cc: Guodong Xu
>> Cc: Haojian Zhuang
>> Cc:
Check for vb2_ops structures that are only stored in the ops field of a
vb2_queue structure. That field is declared const, so vb2_ops structures
that have this property can be declared as const also.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@r
Check for vb2_ops structures that are only stored in the ops field of a
vb2_queue structure. That field is declared const, so vb2_ops structures
that have this property can be declared as const also.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@r
On Mon, Aug 22, 2016 at 3:48 PM, John Stultz wrote:
> This patch reserves some memory in the DTS and sets up a
> pstore device tree node to enable pstore support on HiKey.
>
> Cc: Kees Cook
> Cc: Guodong Xu
> Cc: Haojian
On Mon, Aug 22, 2016 at 3:48 PM, John Stultz wrote:
> This patch reserves some memory in the DTS and sets up a
> pstore device tree node to enable pstore support on HiKey.
>
> Cc: Kees Cook
> Cc: Guodong Xu
> Cc: Haojian Zhuang
> Cc: Wei Xu
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Catalin
Sorry for the delay, I was eaten by a grue.
I found that my initial study did not actually measure the number of
TLB shootdown IPIs sent per TLB shootdown. I think the intuition was
correct but I didn't actually observe what I thought I had; my
original use of probe points was incorrect.
Sorry for the delay, I was eaten by a grue.
I found that my initial study did not actually measure the number of
TLB shootdown IPIs sent per TLB shootdown. I think the intuition was
correct but I didn't actually observe what I thought I had; my
original use of probe points was incorrect.
On Thu, 8 Sep 2016, Fenghua Yu wrote:
> Build the user interface file intel_rdt_rdtgroup.c.
> +obj-$(CONFIG_INTEL_RDT) += intel_rdt.o intel_rdt_rdtgroup.o
> intel_rdt_schemata.o
This is garbage. Complete and utter garbage.
First of all this changelog is wrong because this adds not only
On Thu, 8 Sep 2016, Fenghua Yu wrote:
> Build the user interface file intel_rdt_rdtgroup.c.
> +obj-$(CONFIG_INTEL_RDT) += intel_rdt.o intel_rdt_rdtgroup.o
> intel_rdt_schemata.o
This is garbage. Complete and utter garbage.
First of all this changelog is wrong because this adds not only
On Thu, Sep 8, 2016 at 5:39 PM, Stefan Agner wrote:
> On 2016-09-06 15:40, Leo Li wrote:
>> On Tue, Sep 6, 2016 at 4:51 PM, Stefan Agner wrote:
>>> On 2016-09-06 13:06, Leo Li wrote:
On Tue, Sep 6, 2016 at 1:58 PM, Uwe Kleine-König
On Thu, Sep 8, 2016 at 5:39 PM, Stefan Agner wrote:
> On 2016-09-06 15:40, Leo Li wrote:
>> On Tue, Sep 6, 2016 at 4:51 PM, Stefan Agner wrote:
>>> On 2016-09-06 13:06, Leo Li wrote:
On Tue, Sep 6, 2016 at 1:58 PM, Uwe Kleine-König
wrote:
> On Fri, Aug 19, 2016 at 05:05:22PM
On Thu, 8 Sep 2016, Josh Triplett wrote:
> On Thu, Sep 08, 2016 at 02:19:24PM -0700, John Stultz wrote:
> > On Thu, Sep 8, 2016 at 2:05 PM, Nicolas Pitre wrote:
> > > Small embedded systems typically don't need them. This removes about
> > > 16KB from the kernel binary size on
On Thu, 8 Sep 2016, Josh Triplett wrote:
> On Thu, Sep 08, 2016 at 02:19:24PM -0700, John Stultz wrote:
> > On Thu, Sep 8, 2016 at 2:05 PM, Nicolas Pitre wrote:
> > > Small embedded systems typically don't need them. This removes about
> > > 16KB from the kernel binary size on ARM when
On Thu, 2016-09-08 at 07:48 -0600, Kani, Toshimitsu wrote:
> On Thu, 2016-09-08 at 13:57 +0300, Kirill A. Shutemov wrote:
> >
> > On Mon, Aug 29, 2016 at 10:00:43PM +, Kani, Toshimitsu wrote:
:
> > >
> > > Looking further, these shmem_huge handlings only check pre-
> > > conditions. So, we
On Thu, 2016-09-08 at 07:48 -0600, Kani, Toshimitsu wrote:
> On Thu, 2016-09-08 at 13:57 +0300, Kirill A. Shutemov wrote:
> >
> > On Mon, Aug 29, 2016 at 10:00:43PM +, Kani, Toshimitsu wrote:
:
> > >
> > > Looking further, these shmem_huge handlings only check pre-
> > > conditions. So, we
On Thu, Sep 8, 2016 at 4:33 PM, Frank Rowand wrote:
> On 09/08/16 14:15, Dmitry Shmidt wrote:
>> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>>> On 09/08/16 13:35, dimitr...@google.com wrote:
From
On Thu, Sep 8, 2016 at 4:33 PM, Frank Rowand wrote:
> On 09/08/16 14:15, Dmitry Shmidt wrote:
>> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>>> On 09/08/16 13:35, dimitr...@google.com wrote:
From e14eb45fa5a93c1bff8a6dfe7b6756e4ad72c579 Mon Sep 17 00:00:00 2001
From: Dmitry
On 09/08/16 14:15, Dmitry Shmidt wrote:
> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>> On 09/08/16 13:35, dimitr...@google.com wrote:
>>> From e14eb45fa5a93c1bff8a6dfe7b6756e4ad72c579 Mon Sep 17 00:00:00 2001
>>> From: Dmitry Shmidt
>>>
On 09/08/16 14:15, Dmitry Shmidt wrote:
> On Thu, Sep 8, 2016 at 2:08 PM, Frank Rowand wrote:
>> On 09/08/16 13:35, dimitr...@google.com wrote:
>>> From e14eb45fa5a93c1bff8a6dfe7b6756e4ad72c579 Mon Sep 17 00:00:00 2001
>>> From: Dmitry Shmidt
>>> Date: Wed, 24 Aug 2016 13:25:52 -0700
>>>
101 - 200 of 1900 matches
Mail list logo