On Fri, Feb 24, 2017 at 08:24:42PM +0200, Lucian Zala wrote:
> Hi Greg,
>
> I am a little bit confused regarding your reply, it seems
> that the patch applied afterall, or?
>
>
On Fri, Feb 24, 2017 at 12:10:21PM -0800, SIMRAN SINGHAL wrote:
>
>
> On Friday, February 24, 2017 at 10:46:21 PM UTC+5:30, gregkh wrote:
>
> On Fri, Feb 17, 2017 at 11:20:59PM +0530, simran singhal wrote:
> > Replaces left shift operation (1 << d) by BIT(x) macro.
> >
> > Fix
On Fri, Feb 24, 2017 at 08:24:42PM +0200, Lucian Zala wrote:
> Hi Greg,
>
> I am a little bit confused regarding your reply, it seems
> that the patch applied afterall, or?
>
>
On Fri, Feb 24, 2017 at 12:10:21PM -0800, SIMRAN SINGHAL wrote:
>
>
> On Friday, February 24, 2017 at 10:46:21 PM UTC+5:30, gregkh wrote:
>
> On Fri, Feb 17, 2017 at 11:20:59PM +0530, simran singhal wrote:
> > Replaces left shift operation (1 << d) by BIT(x) macro.
> >
> > Fix
On Sat, Feb 25, 2017 at 04:18:27AM +0530, SIMRAN SINGHAL wrote:
> On Fri, Feb 24, 2017 at 10:47 PM, Greg KH wrote:
> > On Mon, Feb 20, 2017 at 10:41:47PM +0530, simran singhal wrote:
> >> Extra parentheses were causing checkpatch issues
> >> and were removed.
> >>
> >>
On Sat, Feb 25, 2017 at 04:18:27AM +0530, SIMRAN SINGHAL wrote:
> On Fri, Feb 24, 2017 at 10:47 PM, Greg KH wrote:
> > On Mon, Feb 20, 2017 at 10:41:47PM +0530, simran singhal wrote:
> >> Extra parentheses were causing checkpatch issues
> >> and were removed.
> >>
> >> Signed-off-by: simran
No need to check the "if" condition each time, just change it to macro codes.
Signed-off-by: Yunlong Song
---
fs/f2fs/node.h| 10 +-
fs/f2fs/segment.c | 5 +++--
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/fs/f2fs/node.h b/fs/f2fs/node.h
No need to check the "if" condition each time, just change it to macro codes.
Signed-off-by: Yunlong Song
---
fs/f2fs/node.h| 10 +-
fs/f2fs/segment.c | 5 +++--
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/fs/f2fs/node.h b/fs/f2fs/node.h
index 3fc9c4b..caebb23
On Fri, Feb 24, 2017 at 02:05:56PM -0800, Guenter Roeck wrote:
> On 02/24/2017 01:07 PM, Krzysztof Kozlowski wrote:
> > Structures watchdog_device, watchdog_ops and s3c2410_wdt_variant are not
> > modified so they can be made const to increase code safeness.
> >
> > Signed-off-by: Krzysztof
On Fri, Feb 24, 2017 at 02:05:56PM -0800, Guenter Roeck wrote:
> On 02/24/2017 01:07 PM, Krzysztof Kozlowski wrote:
> > Structures watchdog_device, watchdog_ops and s3c2410_wdt_variant are not
> > modified so they can be made const to increase code safeness.
> >
> > Signed-off-by: Krzysztof
Hi Junio,
On Fri, Feb 24, 2017 at 11:28:58AM -0800, Junio C Hamano wrote:
> * Use of an empty string that is used for 'everything matches' is
>still warned and Git asks users to use a more explicit '.' for that
>instead. The hope is that existing users will not mind this
>change,
Hi Junio,
On Fri, Feb 24, 2017 at 11:28:58AM -0800, Junio C Hamano wrote:
> * Use of an empty string that is used for 'everything matches' is
>still warned and Git asks users to use a more explicit '.' for that
>instead. The hope is that existing users will not mind this
>change,
Hi Tyler,
On 2017/2/22 5:22, Tyler Baicar wrote:
> Currently external aborts are unsupported by the guest abort
> handling. Add handling for SEAs so that the host kernel reports
> SEAs which occur in the guest kernel.
>
> Signed-off-by: Tyler Baicar
> ---
>
Hi Tyler,
On 2017/2/22 5:22, Tyler Baicar wrote:
> Currently external aborts are unsupported by the guest abort
> handling. Add handling for SEAs so that the host kernel reports
> SEAs which occur in the guest kernel.
>
> Signed-off-by: Tyler Baicar
> ---
> arch/arm/include/asm/kvm_arm.h
When use device tree mode, user can reserve memory by changes the dts,
however, when boot with ACPI, user cannot reserve memory except by
changing the ACPI table in BIOS, which is not so convenient.
To make user reserve memory for some specific use more convenient,
this patch implement the
When use device tree mode, user can reserve memory by changes the dts,
however, when boot with ACPI, user cannot reserve memory except by
changing the ACPI table in BIOS, which is not so convenient.
To make user reserve memory for some specific use more convenient,
this patch implement the
On Fri, 24 Feb 2017, Tahia Khan wrote:
> Rename struct tstrRSSI to rssi_history_buffer for clarity
> and to remove camel casing.
>
> Signed-off-by: Tahia Khan
Acked-by: Julia Lawall
> ---
> drivers/staging/wilc1000/coreconfigurator.h | 4 ++--
>
On Fri, 24 Feb 2017, Tahia Khan wrote:
> Rename struct tstrRSSI to rssi_history_buffer for clarity
> and to remove camel casing.
>
> Signed-off-by: Tahia Khan
Acked-by: Julia Lawall
> ---
> drivers/staging/wilc1000/coreconfigurator.h | 4 ++--
> 1 file changed, 2 insertions(+), 2
On Sat, 25 Feb 2017, Arushi Singhal wrote:
>
>
> On Fri, Feb 24, 2017 at 10:18 PM, Julia Lawall wrote:
>
>
> On Fri, 24 Feb 2017, Arushi Singhal wrote:
>
> >
> >
> > On Fri, Feb 24, 2017 at 10:01 PM, Greg Kroah-Hartman
> >
On Sat, 25 Feb 2017, Arushi Singhal wrote:
>
>
> On Fri, Feb 24, 2017 at 10:18 PM, Julia Lawall wrote:
>
>
> On Fri, 24 Feb 2017, Arushi Singhal wrote:
>
> >
> >
> > On Fri, Feb 24, 2017 at 10:01 PM, Greg Kroah-Hartman
> > wrote:
> > On Wed, Feb 22,
Remember to use the imperative and to make your subject lines as short as
possible. Here the subject line could be "remove code in comments".
julia
On Sat, 25 Feb 2017, Arushi Singhal wrote:
> Commenting Code Is a Bad Idea.
> Comments are their to explain the code and how the code achieves its
Remember to use the imperative and to make your subject lines as short as
possible. Here the subject line could be "remove code in comments".
julia
On Sat, 25 Feb 2017, Arushi Singhal wrote:
> Commenting Code Is a Bad Idea.
> Comments are their to explain the code and how the code achieves its
Hi Jaegeuk,
I added below diff code into this patch in order to fix incorrectly nid status
updating to reduce large latency of generic/251 in fstest, could you help to
review code below?
Latency:beforeafter
generic/251 1483s ... 184s
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index
Hi Jaegeuk,
I added below diff code into this patch in order to fix incorrectly nid status
updating to reduce large latency of generic/251 in fstest, could you help to
review code below?
Latency:beforeafter
generic/251 1483s ... 184s
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index
On Sat, 25 Feb 2017, Arushi Singhal wrote:
> Error was reported by checkpatch.pl as
> WARNING: Avoid multiple line dereference...
> And If there is boolean operator then it is fixed by Splitting line at
> boolean operator.This is a coding style error.
There is strange spacing and
On Sat, 25 Feb 2017, Arushi Singhal wrote:
> Error was reported by checkpatch.pl as
> WARNING: Avoid multiple line dereference...
> And If there is boolean operator then it is fixed by Splitting line at
> boolean operator.This is a coding style error.
There is strange spacing and
Memory nodes in Arria5, Cyclone5 and Arria10 do not have a unit name.
This will trigger several warnings like this one (when compiled with
W=1):
Node /memory has a reg or ranges property, but no unit name
Add the corresponding unit name to each node.
Signed-off-by: Florian Vaussard
The skeleton.dtsi file is now deprecated as noted in commit 9c0da3cc61f1
("ARM: dts: explicitly mark skeleton.dtsi as deprecated"). The SoCFPGA
device trees already contain the nodes that are defined in skeleton.dtsi
(#address-cells, #size-cells, chosen, aliases, memory).
Including skeleton.dtsi
Most clock nodes in Arria5, Cyclone5 and Arria10 have a reg property but
does not have a unit name. This will trigger several warnings like this
one (when compiled with W=1):
Node /soc/clkmgr@ffd04000/clocks/periph_pll has a reg or ranges
property, but no unit name
Add the corresponding unit
Memory nodes in Arria5, Cyclone5 and Arria10 do not have a unit name.
This will trigger several warnings like this one (when compiled with
W=1):
Node /memory has a reg or ranges property, but no unit name
Add the corresponding unit name to each node.
Signed-off-by: Florian Vaussard
---
The skeleton.dtsi file is now deprecated as noted in commit 9c0da3cc61f1
("ARM: dts: explicitly mark skeleton.dtsi as deprecated"). The SoCFPGA
device trees already contain the nodes that are defined in skeleton.dtsi
(#address-cells, #size-cells, chosen, aliases, memory).
Including skeleton.dtsi
Most clock nodes in Arria5, Cyclone5 and Arria10 have a reg property but
does not have a unit name. This will trigger several warnings like this
one (when compiled with W=1):
Node /soc/clkmgr@ffd04000/clocks/periph_pll has a reg or ranges
property, but no unit name
Add the corresponding unit
Node eccmgr has a unit name, but do not have a reg property as only the
child nodes do have this property. Likewise the usbphy node do not have
a reg property. This will trigger the following warnings when compiled
with W=1:
Node /soc/eccmgr@ffd08140 has a unit name, but no reg property
Node
GPIO LEDs in the Cyclone5 EBV SOCrates board have a unit name but no reg
property. Indeed, GPIO LEDs do not need such a property. They do not
need a unit name neither. This will trigger the following warnings when
compiled with W=1:
Node /gpio-leds/led@0 has a unit name, but no reg property
Node
Node eccmgr has a unit name, but do not have a reg property as only the
child nodes do have this property. Likewise the usbphy node do not have
a reg property. This will trigger the following warnings when compiled
with W=1:
Node /soc/eccmgr@ffd08140 has a unit name, but no reg property
Node
GPIO LEDs in the Cyclone5 EBV SOCrates board have a unit name but no reg
property. Indeed, GPIO LEDs do not need such a property. They do not
need a unit name neither. This will trigger the following warnings when
compiled with W=1:
Node /gpio-leds/led@0 has a unit name, but no reg property
Node
We get a bunch of warnings when compiling the SoCFPGA device trees with W=1.
This warnings happens because some nodes have a unit name but no 'reg' property,
or are missing a unit name while having a 'reg' property. This series enables to
compile all SoCFPGA dts without warnings.
Patches 1 to 5
We get a bunch of warnings when compiling the SoCFPGA device trees with W=1.
This warnings happens because some nodes have a unit name but no 'reg' property,
or are missing a unit name while having a 'reg' property. This series enables to
compile all SoCFPGA dts without warnings.
Patches 1 to 5
The stmpe_touchscreen node in Cyclone5 MCV EVK has a reg property, but
this is not used by the driver. Moreover the binding documentation do
not define this property. Having a reg property without a unit name will
trigger the following warning when compiled with W=1:
Node
The stmpe_touchscreen node in Cyclone5 MCV EVK has a reg property, but
this is not used by the driver. Moreover the binding documentation do
not define this property. Having a reg property without a unit name will
trigger the following warning when compiled with W=1:
Node
On Thu, Feb 23, 2017 at 09:10:39PM +0100, Pavel Machek wrote:
> Hi!
>
>
> > > > > Somehow, startup_32_smp() is on the stack twice. The stack unwind led
> > > > > to the startup_32_smp() frame at 0xf50cdf9c rather than the one at
> > > > > 0xf50cdfa8 (which is where it should normally be). So
On Thu, Feb 23, 2017 at 09:10:39PM +0100, Pavel Machek wrote:
> Hi!
>
>
> > > > > Somehow, startup_32_smp() is on the stack twice. The stack unwind led
> > > > > to the startup_32_smp() frame at 0xf50cdf9c rather than the one at
> > > > > 0xf50cdfa8 (which is where it should normally be). So
Hi Arnaldo,
On Fri, Feb 24, 2017 at 06:08:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Feb 24, 2017 at 10:12:49AM +0900, Namhyung Kim escreveu:
> > The cpu_map__snprint_mask() is to generate string representation of
> > cpumask bitmap. For cpu 0 to 11, it'll return "fff".
> >
> > Cc:
Hi Arnaldo,
On Fri, Feb 24, 2017 at 06:08:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Feb 24, 2017 at 10:12:49AM +0900, Namhyung Kim escreveu:
> > The cpu_map__snprint_mask() is to generate string representation of
> > cpumask bitmap. For cpu 0 to 11, it'll return "fff".
> >
> > Cc:
0-day bot reported some new objtool warnings which were caused by the
new annotate_unreachable() macro:
fs/afs/flock.o: warning: objtool: afs_do_unlk()+0x0: duplicate frame pointer
save
fs/afs/flock.o: warning: objtool: afs_do_unlk()+0x0: frame pointer state
mismatch
0-day bot reported some new objtool warnings which were caused by the
new annotate_unreachable() macro:
fs/afs/flock.o: warning: objtool: afs_do_unlk()+0x0: duplicate frame pointer
save
fs/afs/flock.o: warning: objtool: afs_do_unlk()+0x0: frame pointer state
mismatch
On Fri, Feb 24, 2017 at 7:39 PM, Nick Kralevich wrote:
> Can you try adding the androidboot.selinux=permissive line to the kernel
> command line, to boot in permissive mode? I suspect the policy just needs to
> be adjusted.
Yep. It does seem to boot fine in permissive mode, just
On Fri, Feb 24, 2017 at 7:39 PM, Nick Kralevich wrote:
> Can you try adding the androidboot.selinux=permissive line to the kernel
> command line, to boot in permissive mode? I suspect the policy just needs to
> be adjusted.
Yep. It does seem to boot fine in permissive mode, just not in
On 02/24/2017 12:39 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.10.1 release.
There are 21 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 02/24/2017 12:39 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.10.1 release.
There are 21 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Continue to get mailing wrong message and can not receive some of emails from
linux-f2fs-de...@lists.sourceforge.net, very strange, so send again.
The benefit is much, let me give an example to make the point more clear, the
reserved_sections for a 64G image is
about 500M, and if the current
Continue to get mailing wrong message and can not receive some of emails from
linux-f2fs-de...@lists.sourceforge.net, very strange, so send again.
The benefit is much, let me give an example to make the point more clear, the
reserved_sections for a 64G image is
about 500M, and if the current
On Fri, Feb 24, 2017 at 10:38:38PM +0100, Stefan Wahren wrote:
>
> > Dan Carpenter hat am 24. Februar 2017 um 20:57
> > geschrieben:
> >
> >
> > On Fri, Feb 24, 2017 at 01:37:30PM +0100, Stefan Wahren wrote:
> > > Hi Christophe,
> > >
> > > Am 19.02.2017 um 11:34
On Fri, Feb 24, 2017 at 10:38:38PM +0100, Stefan Wahren wrote:
>
> > Dan Carpenter hat am 24. Februar 2017 um 20:57
> > geschrieben:
> >
> >
> > On Fri, Feb 24, 2017 at 01:37:30PM +0100, Stefan Wahren wrote:
> > > Hi Christophe,
> > >
> > > Am 19.02.2017 um 11:34 schrieb Christophe JAILLET:
On Feb 24, 2017, at 11:59 AM, Greg Kroah-Hartman wrote:
> On Sat, Feb 18, 2017 at 04:47:14PM -0500, James Simmons wrote:
>> From: Alex Zhuravlev
>>
>> on small filesystems plain log can grow dramatically. especially
>> given large record sizes produced by DNE and
On Feb 24, 2017, at 11:59 AM, Greg Kroah-Hartman wrote:
> On Sat, Feb 18, 2017 at 04:47:14PM -0500, James Simmons wrote:
>> From: Alex Zhuravlev
>>
>> on small filesystems plain log can grow dramatically. especially
>> given large record sizes produced by DNE and
On Feb 24, 2017, at 11:59 AM, Greg Kroah-Hartman wrote:
> On Sat, Feb 18, 2017 at 04:47:14PM -0500, James Simmons wrote:
>> From: Alex Zhuravlev
>>
>> on small filesystems plain log can grow dramatically. especially
>> given large record sizes produced by DNE and extended chunksize.
>> I saw
On Feb 24, 2017, at 11:59 AM, Greg Kroah-Hartman wrote:
> On Sat, Feb 18, 2017 at 04:47:14PM -0500, James Simmons wrote:
>> From: Alex Zhuravlev
>>
>> on small filesystems plain log can grow dramatically. especially
>> given large record sizes produced by DNE and extended chunksize.
>> I saw
2017-02-25 12:46 GMT+09:00 Chanwoo Choi :
> Hi,
>
> 2017-02-24 21:02 GMT+09:00 Roger Quadros :
>> +Chanwoo
>>
>> Hi Vivek,
>>
>> On 23/02/17 10:34, Vivek Gautam wrote:
>>>
>>>
>>> On 02/16/2017 06:36 PM, Roger Quadros wrote:
dra7 OTG core limits the host
2017-02-25 12:46 GMT+09:00 Chanwoo Choi :
> Hi,
>
> 2017-02-24 21:02 GMT+09:00 Roger Quadros :
>> +Chanwoo
>>
>> Hi Vivek,
>>
>> On 23/02/17 10:34, Vivek Gautam wrote:
>>>
>>>
>>> On 02/16/2017 06:36 PM, Roger Quadros wrote:
dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
Hi,
2017-02-24 21:02 GMT+09:00 Roger Quadros :
> +Chanwoo
>
> Hi Vivek,
>
> On 23/02/17 10:34, Vivek Gautam wrote:
>>
>>
>> On 02/16/2017 06:36 PM, Roger Quadros wrote:
>>> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
>>> when we're operating in dual-role.
Hi,
2017-02-24 21:02 GMT+09:00 Roger Quadros :
> +Chanwoo
>
> Hi Vivek,
>
> On 23/02/17 10:34, Vivek Gautam wrote:
>>
>>
>> On 02/16/2017 06:36 PM, Roger Quadros wrote:
>>> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
>>> when we're operating in dual-role.
>>>
>>> We work
Can you try adding the androidboot.selinux=permissive line to the kernel
command line, to boot in permissive mode? I suspect the policy just needs
to be adjusted.
-- Nick
On Fri, Feb 24, 2017 at 6:01 PM, John Stultz wrote:
> On Thu, Feb 23, 2017 at 4:01 PM, Paul Moore
Can you try adding the androidboot.selinux=permissive line to the kernel
command line, to boot in permissive mode? I suspect the policy just needs
to be adjusted.
-- Nick
On Fri, Feb 24, 2017 at 6:01 PM, John Stultz wrote:
> On Thu, Feb 23, 2017 at 4:01 PM, Paul Moore wrote:
>> On Thu, Feb 23,
Hi Roger,
[snip]
> /* dwc->lock must be held */
> static void dwc3_otg_core_exit(struct dwc3 *dwc)
> {
> + if (dwc->edev)
> + return;
> +
> /* disable all otg irqs */
> dwc3_otg_disable_events(dwc, DWC3_OTG_ALL_EVENTS);
> /* clear all events */
> @@
Hi Roger,
[snip]
> /* dwc->lock must be held */
> static void dwc3_otg_core_exit(struct dwc3 *dwc)
> {
> + if (dwc->edev)
> + return;
> +
> /* disable all otg irqs */
> dwc3_otg_disable_events(dwc, DWC3_OTG_ALL_EVENTS);
> /* clear all events */
> @@
On Thu, Feb 23, 2017 at 07:40:13PM +0100, Pavel Machek wrote:
> On Thu 2017-02-23 17:28:26, Frederic Weisbecker wrote:
> > On Tue, Feb 14, 2017 at 08:27:43PM +0100, Pavel Machek wrote:
> > > On Tue 2017-02-14 18:59:56, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > > > > Hmm. I moved keyboard
On Thu, Feb 23, 2017 at 07:40:13PM +0100, Pavel Machek wrote:
> On Thu 2017-02-23 17:28:26, Frederic Weisbecker wrote:
> > On Tue, Feb 14, 2017 at 08:27:43PM +0100, Pavel Machek wrote:
> > > On Tue 2017-02-14 18:59:56, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > > > > Hmm. I moved keyboard
On 2017/2/24 6:54, Jaegeuk Kim wrote:
> On 02/23, Chao Yu wrote:
>> On 2017/2/14 10:06, Jaegeuk Kim wrote:
>>> This patches adds bitmaps to represent empty or full NAT blocks containing
>>> free nid entries.
>>>
>>> If we can find valid crc|cp_ver in the last block of checkpoint pack, we'll
>>>
On 2017/2/24 6:54, Jaegeuk Kim wrote:
> On 02/23, Chao Yu wrote:
>> On 2017/2/14 10:06, Jaegeuk Kim wrote:
>>> This patches adds bitmaps to represent empty or full NAT blocks containing
>>> free nid entries.
>>>
>>> If we can find valid crc|cp_ver in the last block of checkpoint pack, we'll
>>>
Rob, thanks for your comments!
El Tue, Feb 21, 2017 at 06:22:14PM -0600 Rob Herring ha dit:
> On Fri, Feb 10, 2017 at 12:43:48PM -0800, Matthias Kaehlcke wrote:
> > The output voltage of a voltage controlled regulator can be controlled
> > through the voltage of another regulator. The current
Rob, thanks for your comments!
El Tue, Feb 21, 2017 at 06:22:14PM -0600 Rob Herring ha dit:
> On Fri, Feb 10, 2017 at 12:43:48PM -0800, Matthias Kaehlcke wrote:
> > The output voltage of a voltage controlled regulator can be controlled
> > through the voltage of another regulator. The current
On Fri, Feb 24, 2017 at 05:40:59PM -0800, Deepa Dinamani wrote:
> Add fields to the superblock to track the min and max
> timestamps supported by filesystems.
>
> Initially, when a superblock is allocated, initialize
> it to the max and min values the fields can hold.
> Individual filesystems
On Fri, Feb 24, 2017 at 05:40:59PM -0800, Deepa Dinamani wrote:
> Add fields to the superblock to track the min and max
> timestamps supported by filesystems.
>
> Initially, when a superblock is allocated, initialize
> it to the max and min values the fields can hold.
> Individual filesystems
Previously kernel message can show that in which function we do the
injection, but unfortunately, most of the caller are the same, for
tracking more information of injection path, it needs to show upper
caller's name. This patch supports that ability.
Signed-off-by: Chao Yu
Previously kernel message can show that in which function we do the
injection, but unfortunately, most of the caller are the same, for
tracking more information of injection path, it needs to show upper
caller's name. This patch supports that ability.
Signed-off-by: Chao Yu
---
Hi Boris,
Thanks for the review
On Sun, Feb 19, 2017 at 3:56 PM, Boris Brezillon
wrote:
> Hi Punnaiah,
>
> Sorry for the late reply.
>
> On Mon, 9 Jan 2017 08:28:54 +0530
> Punnaiah Choudary Kalluri wrote:
>
>> Added
Hi Boris,
Thanks for the review
On Sun, Feb 19, 2017 at 3:56 PM, Boris Brezillon
wrote:
> Hi Punnaiah,
>
> Sorry for the late reply.
>
> On Mon, 9 Jan 2017 08:28:54 +0530
> Punnaiah Choudary Kalluri wrote:
>
>> Added the basic driver for Arasan NAND Flash Controller used in
>> Zynq
On Sat, 2017-02-25 at 05:11 +0530, Arushi Singhal wrote:
> Error was reported by checkpatch.pl as
> WARNING: Avoid multiple line dereference...
> And If there is boolean operator then it is fixed by Splitting line at
> boolean operator.This is a coding style error.
> The changes are made such that
On Sat, 2017-02-25 at 05:11 +0530, Arushi Singhal wrote:
> Error was reported by checkpatch.pl as
> WARNING: Avoid multiple line dereference...
> And If there is boolean operator then it is fixed by Splitting line at
> boolean operator.This is a coding style error.
> The changes are made such that
On 02/01/2017 10:53 AM, Shaohua Li wrote:
> blk_mq_tags/requests of specific hardware queue are mostly used in
> specific cpus, which might not be in the same numa node as disk. For
> example, a nvme card is in node 0. half hardware queue will be used by
> node 0, the other node 1.
Applied 1-3
On 02/01/2017 10:53 AM, Shaohua Li wrote:
> blk_mq_tags/requests of specific hardware queue are mostly used in
> specific cpus, which might not be in the same numa node as disk. For
> example, a nvme card is in node 0. half hardware queue will be used by
> node 0, the other node 1.
Applied 1-3
On Sat, 2017-02-25 at 04:18 +0530, SIMRAN SINGHAL wrote:
> On Fri, Feb 24, 2017 at 10:47 PM, Greg KH wrote:
> > On Mon, Feb 20, 2017 at 10:41:47PM +0530, simran singhal wrote:
> > > Extra parentheses were causing checkpatch issues
> > > and were removed.
> > >
> > >
On Sat, 2017-02-25 at 04:18 +0530, SIMRAN SINGHAL wrote:
> On Fri, Feb 24, 2017 at 10:47 PM, Greg KH wrote:
> > On Mon, Feb 20, 2017 at 10:41:47PM +0530, simran singhal wrote:
> > > Extra parentheses were causing checkpatch issues
> > > and were removed.
> > >
> > > Signed-off-by: simran singhal
On Wed, Feb 22, 2017 at 07:23:38PM +0530, Naveen N. Rao wrote:
> With ABIv2, we offset 8 bytes into a function to get at the local entry
> point.
>
Looks good.
> Signed-off-by: Naveen N. Rao
Acked-by: Ananth N Mavinakayanahalli
On Wed, Feb 22, 2017 at 07:23:38PM +0530, Naveen N. Rao wrote:
> With ABIv2, we offset 8 bytes into a function to get at the local entry
> point.
>
Looks good.
> Signed-off-by: Naveen N. Rao
Acked-by: Ananth N Mavinakayanahalli
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Philippe Reynes
> Sent: Saturday, January 21, 2017 7:06 AM
> To: Kirsher, Jeffrey T ; da...@davemloft.net
> Cc: intel-wired-...@lists.osuosl.org; net...@vger.kernel.org; linux-
>
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Philippe Reynes
> Sent: Saturday, January 21, 2017 7:06 AM
> To: Kirsher, Jeffrey T ; da...@davemloft.net
> Cc: intel-wired-...@lists.osuosl.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org;
The get_ssr_segment happens when need_SSR is true, that is to say we must make
sure we can
achieve a right available SSR segment at least, so why not select the type with
larger probability?
And I think warm and hot are more similar with each other, maybe the update
frequency is difference,
but
The get_ssr_segment happens when need_SSR is true, that is to say we must make
sure we can
achieve a right available SSR segment at least, so why not select the type with
larger probability?
And I think warm and hot are more similar with each other, maybe the update
frequency is difference,
but
On Thu, Feb 23, 2017 at 4:01 PM, Paul Moore wrote:
> On Thu, Feb 23, 2017 at 1:43 PM, John Stultz wrote:
>> Hey folks,
>>I've not been able to figure out why yet, but I wanted to raise the
>> issue that last night I found I couldn't boot Android
On Thu, Feb 23, 2017 at 4:01 PM, Paul Moore wrote:
> On Thu, Feb 23, 2017 at 1:43 PM, John Stultz wrote:
>> Hey folks,
>>I've not been able to figure out why yet, but I wanted to raise the
>> issue that last night I found I couldn't boot Android on my Hikey
>> board with Linus' HEAD kernel.
Hi Linus,
On Fri, Feb 24, 2017 at 02:37:04PM -0800, Linus Torvalds wrote:
This looks like two -tip trees together show some issue - the timer
updates from Thomas triggering a debugobjects check from Ingo, thus
fingering my merge as the culprit.
Added Thomas/Ingo to the cc, leaving everything
Hi Linus,
On Fri, Feb 24, 2017 at 02:37:04PM -0800, Linus Torvalds wrote:
This looks like two -tip trees together show some issue - the timer
updates from Thomas triggering a debugobjects check from Ingo, thus
fingering my merge as the culprit.
Added Thomas/Ingo to the cc, leaving everything
On Fri, Feb 24, 2017 at 5:45 PM, liuxinliang
wrote:
>
>
> On 2017/2/25 9:39, liuxinliang wrote:
>>
>> Hi John,
>>
>> The patch seems good to me, except one minus comment.
>> Maybe change fb_lock to fbdev_lock would be better.
>>
>> Thanks,
>> -xinliang
>>
>> On
On Fri, Feb 24, 2017 at 5:45 PM, liuxinliang
wrote:
>
>
> On 2017/2/25 9:39, liuxinliang wrote:
>>
>> Hi John,
>>
>> The patch seems good to me, except one minus comment.
>> Maybe change fb_lock to fbdev_lock would be better.
>>
>> Thanks,
>> -xinliang
>>
>> On 2017/2/25 9:25, John Stultz wrote:
Quoting James Morse (2017-02-20 03:10:10)
> Hi Stephen,
>
> On 17/02/17 15:53, Stephen Boyd wrote:
> > Quoting James Morse (2017-02-17 03:00:39)
> >> On 17/02/17 01:19, Stephen Boyd wrote:
> >>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
> >>> index 156169c6981b..8bd4e7f11c70
Quoting James Morse (2017-02-20 03:10:10)
> Hi Stephen,
>
> On 17/02/17 15:53, Stephen Boyd wrote:
> > Quoting James Morse (2017-02-17 03:00:39)
> >> On 17/02/17 01:19, Stephen Boyd wrote:
> >>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
> >>> index 156169c6981b..8bd4e7f11c70
On 2017/2/25 9:39, liuxinliang wrote:
Hi John,
The patch seems good to me, except one minus comment.
Maybe change fb_lock to fbdev_lock would be better.
Thanks,
-xinliang
On 2017/2/25 9:25, John Stultz wrote:
In some cases I've been seeing a race where two framebuffers
would be
On 2017/2/25 9:39, liuxinliang wrote:
Hi John,
The patch seems good to me, except one minus comment.
Maybe change fb_lock to fbdev_lock would be better.
Thanks,
-xinliang
On 2017/2/25 9:25, John Stultz wrote:
In some cases I've been seeing a race where two framebuffers
would be
1 - 100 of 1568 matches
Mail list logo