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?
>
> http://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/commit/drivers/staging/fsl-mc?h=staging-testing&id=3bee20
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 th
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 singha
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 100
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 Kozlow
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, and
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 followi
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 deletions
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, 20
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 52d
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 capitalization
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
---
arch/ar
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 i
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 name
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 /soc/
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 fi
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 /soc/i2c@ffc04000/stmpe81
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 th
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: St
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
fs/btrfs/delayed-inode
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 enforcing.
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 ma
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 fre
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 extended chunksize.
>> I saw >5
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 >5
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.
>>>
>>> We work a
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 */
> @@
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 b
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
>>> use
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 ver
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 over
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
---
fs/f2fs/checkpoin
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 UltraScale
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 for
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
> 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; Phili
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 my Hikey
>> board with Linus' HEAD kernel. I
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 qu
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 10064
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 initialized,
On 2017/2/24 23:14, Paolo Bonzini wrote:
On 24/02/2017 16:10, Chris Friesen wrote:
On 02/23/2017 08:23 PM, Herongguang (Stephen) wrote:
On 2017/2/22 22:43, Paolo Bonzini wrote:
Hopefully Gaohuai and Rongguang can help with this too.
Paolo
Yes, we are looking into and testing this.
I
On Fri, Feb 24, 2017 at 5:39 PM, liuxinliang
wrote:
> Hi John,
>
> The patch seems good to me, except one minus comment.
> Maybe change fb_lock to fbdev_lock would be better.
Sure I'll change that too, but I'll wait before next week before
resending to see if anyone else has feedback.
thanks
-jo
Allow read only mounts for filesystems that do not
have maximum timestamps beyond the y2038 expiry
timestamp.
Also, allow a sysctl override to all such filesystems
to be mounted with write permissions.
A boot param supports initial override of these
checks from the early boot without recompilation
timespec_trunc() function is used to truncate a
filesystem timestamp to the right granularity.
But, the function does not clamp tv_sec part of the
timestamps according to the filesystem timestamp limits.
Also, timespec_trunc() is exclusively used for filesystem
timestamps. Move the api to be part
POSIX.1 section for futimens, utimensat and utimes says:
The file's relevant timestamp shall be set to the
greatest value supported by the file system that is
not greater than the specified time.
Clamp the timestamps accordingly before assignment.
Note that the clamp_t macro is used for clamping
The series is aimed at adding timestamp checking and policy
related to it to vfs.
The series was developed with discussions and guidance from
Arnd Bergmann.
The original thread is at https://lkml.org/lkml/2016/11/2/294
Associated test: xfstests generic/402
Note that the above test will be run an
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 override these to match their
actual limits.
Pseudo filesystems are assumed to
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani
Cc: "Theodore Ts'o"
Cc: Andreas Dilger
Cc: linux-e...@vger.kernel.org
---
fs/ext4/ext4.h | 4
fs/ext4/super.c | 7 ++-
2 files changed, 10 insertions(+),
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 initialized, as kirin_fbdev_output_poll_changed()
mig
In some cases I've been seeing a race where two framebuffers
would be initialized, as kirin_fbdev_output_poll_changed()
might get called quickly in succession, resulting in the
initialization happening twice. This could cause the system
to boot up with a blank screen.
This patch adds a simple mute
On 2017/2/25 5:33, John Stultz wrote:
On Thu, Feb 23, 2017 at 5:55 PM, liuxinliang
wrote:
Hi John,
On 2017/2/23 8:56, John Stultz wrote:
In some cases I've been seeing a race where two framebuffers
would be initialized, as kirin_fbdev_output_poll_changed()
might get called quickly in succes
Quoting Stephen Boyd (2017-02-17 08:52:29)
> If we call get_user() with an __le* or __be* type sparse will
> complain when we assign the result to 0 on the faulting path.
> Let's force cast here so that sparse doesn't complain. This
> mirrors what we do in __get_user() as well.
>
> Signed-off-by:
Hi Linus,
My for-linus-4.11 branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
for-linus-4.11
Has a series of fixes and cleanups that Dave Sterba has been collecting:
There is a pretty big variety here, cleaning up internal APIs and fixing
corner cases.
David Sterba
On Fri, Feb 24, 2017 at 11:37 PM, Seunghun Han wrote:
> Hi, Rafael.
>
> I agree with you and I added my opinion below.
>
> 2017-02-25 1:50 GMT+09:00 Rafael J. Wysocki :
>> On Friday, February 24, 2017 09:56:21 PM Seunghun Han wrote:
>>> Hi, Rafeal.
>>>
>>> I added my opinion below.
>>>
>>> 2017-02
On 2017/2/25 2:12, Jaegeuk Kim wrote:
> On 02/24, Yunlong Song wrote:
>> On 2017/2/24 19:37, Chao Yu wrote:
>>> On 2017/2/24 19:11, Yunlong Song wrote:
I think we do not need to care about the CP_CRC_RECOVERY_FLAG status of
old image, I mean we
do not need to check the already-been-
On Fri, Feb 24, 2017 at 06:43:27PM -0500, James Bottomley wrote:
> > It just seems confusing to call something a namespace that isn't also
> > a CLONE_NEW* option..
>
> Well, there's namespace behaviour and then there's how you enter them.
> We have namespace behaviour with the /dev/tpms but th
On 2/24/2017 2:46 PM, John Stultz wrote:
> Hey John,
> So after the USB tree landed in 4.11-rc, I've been seeing the
> following warning at bootup.
>
> It seems the fifo_mem/total_fifo_size value on hikey is 1920, but I'm
> seeing the addresses zip upward quickly as the txfsz values are all
> 204
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 48 +++
1 file changed, 48 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index cfc7edc8fb15..4e16fedad5ec 100644
--- a/arch/arm64
From: Brian Ashworth
The pivot_root syscall is not needed on systems that do not use
any intermediate filesystem. Allowing for pivot_root to be
ommitted from the kernel will aid in the tinification efforts.
Without CONFIG_PIVOT_ROOT_SYSCALL set
add/remove: 0/1 grow/shrink: 0/0 up/down: 0/-614 (-
From: Brian Ashworth
add/remove: 0/0 grow/shrink: 1/0 up/down: 4/0 (4)
function old new delta
sys_pivot_root 610 614 +4
Total: Before=1899573, After=1899577, chg +0.00%
Signed-off-by Brian Ashworth
---
fs/Makefile
From: Brian Ashworth
add/remove: 1/0 grow/shrink: 0/2 up/down: 19/-44 (-25)
function old new delta
detach_mnt - 19 +19
attach_recursive_mnt 349 331 -18
sys_pivot_root
From: Brian Ashworth
This patch series will allow for the pivot_root syscall to be made
optional. The first patch refactors the functions that are required
by pivot_root so they can be accessed outside of fs/namespace.c. The
second patch moves the pivot_root syscall to its own file. The third
add
The mm-of-the-moment snapshot 2017-02-24-16-18 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
From: Niklas Cassel
SIGKILL has been sent, but the task is stuck in down_read (after do_exit),
even though no task is doing down_write on the rwsem in question.
INFO: task libupnp:21868 blocked for more than 120 seconds.
Tainted: G O4.9.11-devel #1
"echo 0 > /proc/sys/kernel/
On Tue 2017-02-21 13:11:04, Sakari Ailus wrote:
> On Tue, Feb 21, 2017 at 12:07:21PM +0100, Pavel Machek wrote:
> > On Mon 2017-02-20 15:56:36, Sakari Ailus wrote:
> > > On Mon, Feb 20, 2017 at 03:09:13PM +0200, Sakari Ailus wrote:
> > > > I've tested ACPI, will test DT soon...
> > >
> > > DT case
On Fri, 24 Feb 2017 17:11:03 -0300
Arnaldo Carvalho de Melo wrote:
> Em Sat, Feb 25, 2017 at 02:29:17AM +0900, Masami Hiramatsu escreveu:
> > On Fri, 24 Feb 2017 00:46:08 +0530
> > "Naveen N. Rao" wrote:
> > > Thanks. I hope that's an Ack for this patchset?
> >
> > OK, for 1/5, 2/5, 3/5, and 5/
Am 24.02.2017 um 04:40 schrieb Andreas Färber:
> + uart2: serial@b0124000 {
> + compatible = "actions,s500-uart", "actions,owl-uart";
> + reg = <0xb0126000 0x2000>;
Wrong reg offset.
> + interrupts = ;
> +
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 the other errors does not generate
beacause of this change like lin
From: Eric Biggers
Constify the buffer passed to crypto_kpp_set_secret() and
kpp_alg.set_secret, since it is never modified.
Signed-off-by: Eric Biggers
---
crypto/dh.c | 3 ++-
crypto/ecdh.c | 3 ++-
drivers/crypto/qat/qat_comm
From: Eric Biggers
Cryptographic test vectors should never be modified, so constify them to
enforce this at both compile-time and run-time. This moves a significant
amount of data from .data to .rodata when the crypto tests are enabled.
Signed-off-by: Eric Biggers
---
crypto/testmgr.c | 71 +
From: Eric Biggers
These two patches mark all the cryptographic test vectors as 'const'.
This has several potential advantages and moves a large amount of data
from .data to .rodata when the tests are enabled. The second patch does
the real work; the first just prepares for it by updating a func
On Fri, 2017-02-24 at 16:23 -0700, Jason Gunthorpe wrote:
> On Fri, Feb 24, 2017 at 06:01:00PM -0500, James Bottomley wrote:
>
> > Well, as a glib answer, I'd say the TPM is a device, so the thing
> > which restricts device access to containers is the device cgroup
> > ... that's what we should
Hi Shaohua,
On Thu, Feb 23, 2017 at 10:15:50PM -0800, Shaohua Li wrote:
> On Fri, Feb 24, 2017 at 10:49:39AM +0900, Minchan Kim wrote:
> > On Wed, Feb 22, 2017 at 10:50:41AM -0800, Shaohua Li wrote:
> > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous
> > > pages, but they
On 02/24/2017 01:45 PM, Ard Biesheuvel wrote:
> On 24 February 2017 at 21:25, John Stultz wrote:
>> On Thu, Feb 23, 2017 at 10:43 AM, Laura Abbott wrote:
>>> Hi,
>>>
>>> Fedora was previously carrying a workaround for a gcc7 issue reported
>>> on arm64
>>> http://lists.infradead.org/pipermail/li
Hi Linus,
(notes there may me minor conflicts for this merge, if its anything bad
let me know)
- scripts/checkstack.pl - nios and openrisc seem to have came in at the
same time
- arch/openrisc/include/asm/Kbuild - Ingo's PULL of the cputime changes
removed headers in the same place
Please
The following changes since commit 318fa46cc60d37fec1e87dbf03a82aca0f5ce695:
clk/samsung: exynos542x: mark some clocks as critical (2017-01-09 16:11:05
-0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-for-linus
for you to f
Hi Johannes,
On Fri, Feb 24, 2017 at 10:36:55AM -0500, Johannes Weiner wrote:
> On Fri, Feb 24, 2017 at 11:12:18AM +0900, Minchan Kim wrote:
> > > @@ -1525,8 +1531,8 @@ int try_to_unmap(struct page *page, enum ttu_flags
> > > flags)
> > >
> > > if (ret != SWAP_MLOCK && !page_mapcount(page)) {
Am 24.02.2017 um 23:29 schrieb Daniel Lezcano:
> On Fri, Feb 24, 2017 at 04:40:42AM +0100, Andreas Färber wrote:
>> Implement clocksource and clockevents for Actions Semi S500.
>>
>> Based on LeMaker linux-actions tree.
>>
>> Signed-off-by: Andreas Färber
>
> As this is a new driver, please give
On Fri, Feb 24, 2017 at 06:01:00PM -0500, James Bottomley wrote:
> Well, as a glib answer, I'd say the TPM is a device, so the thing which
> restricts device access to containers is the device cgroup ... that's
> what we should be plugging into. I'd have to look, but I suspect the
> device cgroup
Hi,
This oops
[1.616381] sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels
[1.616505] BUG: unable to handle kernel NULL pointer dereference
at 07ab
[1.616512] IP: [] device_to_iommu+0x11a/0x1a0
[1.616515] PGD 0
[1.616518] Oops: [#1] SMP
[1.616563
Commenting Code Is a Bad Idea.
Comments are their to explain the code and how the code achieves its
goal and as codes in the comments does not explain what the code is
doing so there is no use of commenting them.
So in thos patch codes in the comments are removed.
Signed-off-by: Arushi Singhal
-
On 02/24/2017 03:29 PM, Bjorn Helgaas wrote:
> On Wed, Feb 01, 2017 at 09:53:15AM -0800, Shaohua Li wrote:
>> Next patch will use the API to get the node from vector for nvme device
>>
>> Signed-off-by: Shaohua Li
>
> Acked-by: Bjorn Helgaas
>
> Sorry I missed this; I normally work from the lin
Thanks Al... I was going to try and evaluate that patch next
week, now all I have to do is test it ...
-Mike
On Fri, Feb 24, 2017 at 3:52 PM, Al Viro wrote:
> That, AFAICS, fixes a real bug. Applied, and it needs Cc:stable as well.
>
>
>> Signed-off-by: Peter Zijlstra (Intel)
>> ---
>> fs/or
On Fri, 2017-02-24 at 13:52 -0700, Jason Gunthorpe wrote:
> On Fri, Feb 24, 2017 at 03:29:15PM -0500, James Bottomley wrote:
> > On Fri, 2017-02-24 at 11:11 -0700, Jason Gunthorpe wrote:
> > > On Fri, Feb 24, 2017 at 07:39:22PM +0200, Jarkko Sakkinen wrote:
> > >
> > > > > I think therefore that t
The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace
operation to specify if registers need to saved/restored by the ftrace handler.
This is needed by kgraft and possibly other ftrace-based tools, and the ARM
architecture is currently lacking this feature. It would also be the
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
>> ---
>>
>> v2:
>>-Removed parentheses around argument of cast
>>
On Fri, Feb 24, 2017 at 3:59 AM, Yong Mao wrote:
> Dear Rob,
>
> Could you please help to make comments for this patch?
> Thanks.
I already did comment. It's still wrong as Ulf commented. So fix and
send a new version. It has to go to the DT list if you want to be in
my queue.
Rob
Hey John,
So after the USB tree landed in 4.11-rc, I've been seeing the
following warning at bootup.
It seems the fifo_mem/total_fifo_size value on hikey is 1920, but I'm
seeing the addresses zip upward quickly as the txfsz values are all
2048. Not exactly sure whats wrong here. Things still s
On Thu, Feb 23, 2017 at 03:56:21PM -0700, Logan Gunthorpe wrote:
>
>
> On 23/02/17 03:43 PM, Bjorn Helgaas wrote:
> > This path seems a little generic. I don't see other cases where a
> > product brand name ("Switchtec") appears at the top level of
> > /sys/class/...
>
> Ok, well we are certain
Hi, Rafael.
I agree with you and I added my opinion below.
2017-02-25 1:50 GMT+09:00 Rafael J. Wysocki :
> On Friday, February 24, 2017 09:56:21 PM Seunghun Han wrote:
>> Hi, Rafeal.
>>
>> I added my opinion below.
>>
>> 2017-02-24 21:13 GMT+09:00 Rafael J. Wysocki :
>> > On Friday, February 24,
1 - 100 of 784 matches
Mail list logo
