On Wed, Jul 20, 2016 at 11:36 AM, Hoan Tran wrote:
> On Fri, Jul 1, 2016 at 5:09 PM, Hoan Tran wrote:
>>
>> Hi Stephen,
>>
>> On Fri, Jul 1, 2016 at 11:38 AM, Stephen Boyd wrote:
>> > Sorry I replied offlist before. Pressed the wrong key.
>>
On Wed, Jul 20, 2016 at 11:36 AM, Hoan Tran wrote:
> On Fri, Jul 1, 2016 at 5:09 PM, Hoan Tran wrote:
>>
>> Hi Stephen,
>>
>> On Fri, Jul 1, 2016 at 11:38 AM, Stephen Boyd wrote:
>> > Sorry I replied offlist before. Pressed the wrong key.
>> >
>> > On 06/30, Hoan Tran wrote:
>> >> On Thu, Jun
No textual changes beyond formatting.
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Dmitry Vyukov
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/kasan.rst | 173
No textual changes beyond formatting.
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Dmitry Vyukov
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/kasan.rst | 173 ++
Documentation/dev-tools/tools.rst | 1 +
Documentation/kasan.txt
Fold the sparse document into the development tools set; no changes to the
text itself beyond formatting.
Signed-off-by: Jonathan Corbet
---
Documentation/{sparse.txt => dev-tools/sparse.rst} | 61 +-
Documentation/dev-tools/tools.rst | 1 +
On 08/08, Masahiro Yamada wrote:
> Hi Stephen,
>
>
> 2016-08-05 6:25 GMT+09:00 Stephen Boyd :
> > +Rob in case he has any insight
> >
> > On 07/09, Masahiro Yamada wrote:
> >> Hi.
> >>
> >> I think the current code allows to add
> >> clk_providers multiple times against one
Cc: Andrey Ryabinin
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/tools.rst| 1 +
Documentation/{ubsan.txt => dev-tools/ubsan.rst} | 42 +---
2 files changed, 24 insertions(+), 19 deletions(-)
rename
Fold the sparse document into the development tools set; no changes to the
text itself beyond formatting.
Signed-off-by: Jonathan Corbet
---
Documentation/{sparse.txt => dev-tools/sparse.rst} | 61 +-
Documentation/dev-tools/tools.rst | 1 +
2 files
On 08/08, Masahiro Yamada wrote:
> Hi Stephen,
>
>
> 2016-08-05 6:25 GMT+09:00 Stephen Boyd :
> > +Rob in case he has any insight
> >
> > On 07/09, Masahiro Yamada wrote:
> >> Hi.
> >>
> >> I think the current code allows to add
> >> clk_providers multiple times against one DT node.
> >>
> >>
Cc: Andrey Ryabinin
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/tools.rst| 1 +
Documentation/{ubsan.txt => dev-tools/ubsan.rst} | 42 +---
2 files changed, 24 insertions(+), 19 deletions(-)
rename Documentation/{ubsan.txt =>
Cc: Catalin Marinas
Signed-off-by: Jonathan Corbet
---
.../{kmemleak.txt => dev-tools/kmemleak.rst} | 93 --
Documentation/dev-tools/tools.rst | 1 +
MAINTAINERS| 2 +-
Cc: Catalin Marinas
Signed-off-by: Jonathan Corbet
---
.../{kmemleak.txt => dev-tools/kmemleak.rst} | 93 --
Documentation/dev-tools/tools.rst | 1 +
MAINTAINERS| 2 +-
3 files changed, 52 insertions(+), 44
No textual changes have been made, but the formatting has obviously been
tweaked.
Cc: Michal Marek
Cc: Gilles Muller
Cc: Nicolas Palix
Cc: Julia Lawall
Signed-off-by: Jonathan Corbet
---
Another document added to the dev-tools collection.
Cc: Dmitry Vyukov
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/kcov.rst | 111 ++
Documentation/dev-tools/tools.rst | 1 +
Documentation/kcov.txt
Cc: Vegard Nossum
Cc: Pekka Enberg
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/kmemcheck.rst | 733 +
Documentation/dev-tools/tools.rst | 1 +
Documentation/kmemcheck.txt |
No textual changes beyond formatting.
Cc: Peter Oberparleiter
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/gcov.rst | 256 +
Documentation/dev-tools/tools.rst | 1 +
Documentation/gcov.txt
Cc: Jan Kiszka
Signed-off-by: Jonathan Corbet
---
.../gdb-kernel-debugging.rst} | 77 +-
Documentation/dev-tools/tools.rst | 1 +
2 files changed, 46 insertions(+), 32 deletions(-)
rename
No textual changes have been made, but the formatting has obviously been
tweaked.
Cc: Michal Marek
Cc: Gilles Muller
Cc: Nicolas Palix
Cc: Julia Lawall
Signed-off-by: Jonathan Corbet
---
.../{coccinelle.txt => dev-tools/coccinelle.rst} | 359 +++--
Another document added to the dev-tools collection.
Cc: Dmitry Vyukov
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/kcov.rst | 111 ++
Documentation/dev-tools/tools.rst | 1 +
Documentation/kcov.txt| 111
Cc: Vegard Nossum
Cc: Pekka Enberg
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/kmemcheck.rst | 733 +
Documentation/dev-tools/tools.rst | 1 +
Documentation/kmemcheck.txt | 754 --
MAINTAINERS
No textual changes beyond formatting.
Cc: Peter Oberparleiter
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/gcov.rst | 256 +
Documentation/dev-tools/tools.rst | 1 +
Documentation/gcov.txt| 257
Cc: Jan Kiszka
Signed-off-by: Jonathan Corbet
---
.../gdb-kernel-debugging.rst} | 77 +-
Documentation/dev-tools/tools.rst | 1 +
2 files changed, 46 insertions(+), 32 deletions(-)
rename Documentation/{gdb-kernel-debugging.txt =>
This directory will be a collecting point for documentation oriented around
development tools. As a step toward ordering Documentation/ it's a small
one, but we have to start somewhere...
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/tools.rst | 16
This directory will be a collecting point for documentation oriented around
development tools. As a step toward ordering Documentation/ it's a small
one, but we have to start somewhere...
Signed-off-by: Jonathan Corbet
---
Documentation/dev-tools/tools.rst | 16
This series of patches collects a number of documents related to kernel
development tools, converts them to the Sphinx format, and puts them
together into the dev-tools directory. The resulting formatted
documentation can be seen at:
http://static.lwn.net/kerneldoc/dev-tools/tools.html
This series of patches collects a number of documents related to kernel
development tools, converts them to the Sphinx format, and puts them
together into the dev-tools directory. The resulting formatted
documentation can be seen at:
http://static.lwn.net/kerneldoc/dev-tools/tools.html
On 8/8/2016 5:53 PM, Stephen Rothwell wrote:
> Hi Doug,
>
> On Mon, 8 Aug 2016 11:37:33 -0400 Doug Ledford wrote:
>>
>> On 8/7/2016 9:58 PM, Stephen Rothwell wrote:
>>>
>>> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed
>>> like this:
>>>
>>>
On 8/8/2016 5:53 PM, Stephen Rothwell wrote:
> Hi Doug,
>
> On Mon, 8 Aug 2016 11:37:33 -0400 Doug Ledford wrote:
>>
>> On 8/7/2016 9:58 PM, Stephen Rothwell wrote:
>>>
>>> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed
>>> like this:
>>>
>>>
Guided by grsecurity's analogous __read_only markings in arch/x86,
this applies several uses of __ro_after_init to structures that are
only updated during __init, and const for some structures that are
never updated. Additionally extends __init markings to some functions
that are only used during
Guided by grsecurity's analogous __read_only markings in arch/x86,
this applies several uses of __ro_after_init to structures that are
only updated during __init, and const for some structures that are
never updated. Additionally extends __init markings to some functions
that are only used during
Hi Baoquan,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.8-rc1 next-20160808]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Baoquan-He/ACPI-tables-Correct-the-wrong
Hi Baoquan,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.8-rc1 next-20160808]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Baoquan-He/ACPI-tables-Correct-the-wrong
On Mon, Aug 8, 2016 at 4:20 PM, Kees Cook wrote:
> On Mon, Aug 8, 2016 at 4:03 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
On Mon, Aug 8, 2016 at 4:20 PM, Kees Cook wrote:
> On Mon, Aug 8, 2016 at 4:03 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:
From: Dave Hansen
This is all that we need to get the new system calls themselves
working on x86.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux-a...@vger.kernel.org
Cc: linux...@kvack.org
Cc: x...@kernel.org
Cc:
On Mon, Aug 8, 2016 at 4:03 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
From: Dave Hansen
This is all that we need to get the new system calls themselves
working on x86.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux-a...@vger.kernel.org
Cc: linux...@kvack.org
Cc: x...@kernel.org
Cc: torva...@linux-foundation.org
Cc: a...@linux-foundation.org
On Mon, Aug 8, 2016 at 4:03 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
From: Dave Hansen
PF_PK means that a memory access violated the protection key
access restrictions. It is unconditionally an access_error()
because the permissions set on the VMA don't matter (the PKRU
value overrides it), and we never "resolve" PK faults (like
how
From: Dave Hansen
This patch adds two new system calls:
int pkey_alloc(unsigned long flags, unsigned long init_access_rights)
int pkey_free(int pkey);
These implement an "allocator" for the protection keys
themselves, which can be thought of as
From: Dave Hansen
PF_PK means that a memory access violated the protection key
access restrictions. It is unconditionally an access_error()
because the permissions set on the VMA don't matter (the PKRU
value overrides it), and we never "resolve" PK faults (like
how a COW can "resolve write
From: Dave Hansen
This patch adds two new system calls:
int pkey_alloc(unsigned long flags, unsigned long init_access_rights)
int pkey_free(int pkey);
These implement an "allocator" for the protection keys
themselves, which can be thought of as analogous to the allocator
that
From: Dave Hansen
This code should be a good demonstration of how to use the new
system calls as well as how to use protection keys in general.
This code shows how to:
1. Manipulate the Protection Keys Rights User (PKRU) register
2. Set a protection key on memory
From: Dave Hansen
pkey_mprotect() is just like mprotect, except it also takes a
protection key as an argument. On systems that do not support
protection keys, it still works, but requires that key=0.
Otherwise it does exactly what mprotect does.
I expect it to get
From: Dave Hansen
These new syscalls are implemented as generic code, so enable
them for architectures like arm64 which use the generic syscall
table.
According to Arnd:
Even if the support is x86 specific for the forseeable
future, it may be good
From: Dave Hansen
PKRU is the register that lets you disallow writes or all access
to a given protection key.
The XSAVE hardware defines an "init state" of 0 for PKRU: its
most permissive state, allowing access/writes to everything.
Since we start off all new
From: Dave Hansen
pkey_mprotect() is just like mprotect, except it also takes a
protection key as an argument. On systems that do not support
protection keys, it still works, but requires that key=0.
Otherwise it does exactly what mprotect does.
I expect it to get used like this, if you want
From: Dave Hansen
These new syscalls are implemented as generic code, so enable
them for architectures like arm64 which use the generic syscall
table.
According to Arnd:
Even if the support is x86 specific for the forseeable
future, it may be good to reserve the number just in
From: Dave Hansen
PKRU is the register that lets you disallow writes or all access
to a given protection key.
The XSAVE hardware defines an "init state" of 0 for PKRU: its
most permissive state, allowing access/writes to everything.
Since we start off all new processes with the init state, we
From: Dave Hansen
This code should be a good demonstration of how to use the new
system calls as well as how to use protection keys in general.
This code shows how to:
1. Manipulate the Protection Keys Rights User (PKRU) register
2. Set a protection key on memory
3. Fetch and/or modify PKRU
On Mon, Aug 8, 2016 at 3:38 PM, Linus Torvalds
wrote:
> On Tue, Aug 2, 2016 at 3:20 PM, Kees Cook wrote:
>>
>> Please pull this new gcc-plugin for v4.8-rc1.
>
> So I'm not pulling this for four reasons:
>
> (a) most of it is back-merges.
On Mon, Aug 8, 2016 at 3:38 PM, Linus Torvalds
wrote:
> On Tue, Aug 2, 2016 at 3:20 PM, Kees Cook wrote:
>>
>> Please pull this new gcc-plugin for v4.8-rc1.
>
> So I'm not pulling this for four reasons:
>
> (a) most of it is back-merges. There are 8 actual commits - but they
> are preceded by
From: Dave Hansen
This spells out all of the pkey-related system calls that we have
and provides some example code fragments to demonstrate how we
expect them to be used.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc:
From: Dave Hansen
This spells out all of the pkey-related system calls that we have
and provides some example code fragments to demonstrate how we
expect them to be used.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux-a...@vger.kernel.org
Cc: linux...@kvack.org
Cc:
Since the last post, I've slightly updated the wording in one of
the patch descriptions but have made no code changes.
I think this is ready to be pulled into the x86 tree.
Note, this set depends on a previously submitted patch to be
applied before it will function:
From: Dave Hansen
Today, mprotect() takes 4 bits of data: PROT_READ/WRITE/EXEC/NONE.
Three of those bits: READ/WRITE/EXEC get translated directly in to
vma->vm_flags by calc_vm_prot_bits(). If a bit is unset in
mprotect()'s 'prot' argument then it must be cleared
Since the last post, I've slightly updated the wording in one of
the patch descriptions but have made no code changes.
I think this is ready to be pulled into the x86 tree.
Note, this set depends on a previously submitted patch to be
applied before it will function:
From: Dave Hansen
Today, mprotect() takes 4 bits of data: PROT_READ/WRITE/EXEC/NONE.
Three of those bits: READ/WRITE/EXEC get translated directly in to
vma->vm_flags by calc_vm_prot_bits(). If a bit is unset in
mprotect()'s 'prot' argument then it must be cleared in vma->vm_flags
during the
From: Dave Hansen
As discussed in the previous patch, there is a reliability
benefit to allowing an init value for the Protection Keys Rights
User register (PKRU) which differs from what the XSAVE hardware
provides.
But, having PKRU be 0 (its init value) provides
From: Dave Hansen
As discussed in the previous patch, there is a reliability
benefit to allowing an init value for the Protection Keys Rights
User register (PKRU) which differs from what the XSAVE hardware
provides.
But, having PKRU be 0 (its init value) provides some nonzero
amount of
On Thu, Aug 04, 2016 at 05:22:32PM -0500, Josh Poimboeuf wrote:
> With frame pointers, when a task is interrupted, its stack is no longer
> completely reliable because the function could have been interrupted
> before it had a chance to save the previous frame pointer on the stack.
> So the caller
On Thu, Aug 04, 2016 at 05:22:32PM -0500, Josh Poimboeuf wrote:
> With frame pointers, when a task is interrupted, its stack is no longer
> completely reliable because the function could have been interrupted
> before it had a chance to save the previous frame pointer on the stack.
> So the caller
From: Xinliang Liu
Add ade and dsi DT nodes for hikey board.
Cc: Guodong Xu
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will
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
From: Xinliang Liu
Add adv7533 HDMI DT node for HiKey board.
Cc: Guodong Xu
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will
Add support to hikey dts for the syscon-reboot-mode driver.
After trying an approach using a sram driver and node, a number
of issues cropped up which would make it so we would be
duplicating a lot of extra syscon infrastructure in order to
support mfds on sram. After talking with Bjorn, using
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 Marinas
Cc: Will Deacon
Cc: linux-arm-ker...@lists.infradead.org
Cc:
From: Xinliang Liu
Add adv7533 HDMI DT node for HiKey board.
Cc: Guodong Xu
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will Deacon
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Signed-off-by: Xinliang Liu
Signed-off-by: John Stultz
---
Add support to hikey dts for the syscon-reboot-mode driver.
After trying an approach using a sram driver and node, a number
of issues cropped up which would make it so we would be
duplicating a lot of extra syscon infrastructure in order to
support mfds on sram. After talking with Bjorn, using
From: Xinliang Liu
Add ade and dsi DT nodes for hikey board.
Cc: Guodong Xu
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will Deacon
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Signed-off-by: Xinliang Liu
Signed-off-by: John Stultz
---
The current code always increases the count in the 1st element of
array proc[].
Signed-off-by: Baoquan He
Cc: Rafael J. Wysocki
Cc: Len Brown
Cc: linux-a...@vger.kernel.org
---
drivers/acpi/tables.c | 2 +-
1 file changed, 1 insertion(+),
The current code always increases the count in the 1st element of
array proc[].
Signed-off-by: Baoquan He
Cc: Rafael J. Wysocki
Cc: Len Brown
Cc: linux-a...@vger.kernel.org
---
drivers/acpi/tables.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/tables.c
It won't impact the result, we still should fix the code bug.
Signed-off-by: Baoquan He
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Cc: Pavel Machek
Cc: Thomas Gleixner
Cc: Ingo Molnar
It won't impact the result, we still should fix the code bug.
Signed-off-by: Baoquan He
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Cc: Pavel Machek
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: x...@kernel.org
Cc: linux...@vger.kernel.org
---
arch/x86/kernel/acpi/boot.c | 4 ++--
On 08/08/2016 05:02 AM, Michael Ellerman wrote:
> James Bottomley writes:
>
>> This is seven basic fixes (plus one MAINTAINERS update) which came in
>> close to the merge window.
>>
>> The patch is available here:
>>
>>
On 08/08/2016 05:02 AM, Michael Ellerman wrote:
> James Bottomley writes:
>
>> This is seven basic fixes (plus one MAINTAINERS update) which came in
>> close to the merge window.
>>
>> The patch is available here:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-misc
>>
>>
On Mon, 8 Aug 2016 10:29:05 -0400
David Long wrote:
> >> @@ -489,20 +477,15 @@ int __kprobes setjmp_pre_handler(struct kprobe
> >> *p, struct pt_regs *regs)
> >> {
> >> struct jprobe *jp = container_of(p, struct jprobe, kp);
> >> struct kprobe_ctlblk *kcb =
On Mon, 8 Aug 2016 10:29:05 -0400
David Long wrote:
> >> @@ -489,20 +477,15 @@ int __kprobes setjmp_pre_handler(struct kprobe
> >> *p, struct pt_regs *regs)
> >> {
> >> struct jprobe *jp = container_of(p, struct jprobe, kp);
> >> struct kprobe_ctlblk *kcb = get_kprobe_ctlblk();
> >> -
Hi Brian,
On Thu, 4 Aug 2016 12:37:51 +0800
Brian Norris wrote:
> Hi Boris,
>
> On Mon, Jun 20, 2016 at 03:50:16PM +0200, Boris Brezillon wrote:
> > MLC and TLC NAND devices are using NAND cells exposing more than one bit,
> > but instead of attaching all the bits
Hi Brian,
On Thu, 4 Aug 2016 12:37:51 +0800
Brian Norris wrote:
> Hi Boris,
>
> On Mon, Jun 20, 2016 at 03:50:16PM +0200, Boris Brezillon wrote:
> > MLC and TLC NAND devices are using NAND cells exposing more than one bit,
> > but instead of attaching all the bits in a given cell to a single
On Tue, Aug 2, 2016 at 3:20 PM, Kees Cook wrote:
>
> Please pull this new gcc-plugin for v4.8-rc1.
So I'm not pulling this for four reasons:
(a) most of it is back-merges. There are 8 actual commits - but they
are preceded by 11 pointless merges of the kbuild branch. No
On Tue, Aug 2, 2016 at 3:20 PM, Kees Cook wrote:
>
> Please pull this new gcc-plugin for v4.8-rc1.
So I'm not pulling this for four reasons:
(a) most of it is back-merges. There are 8 actual commits - but they
are preceded by 11 pointless merges of the kbuild branch. No thank
you.
(b) of the
This patch add the IMEM syscon memory region to the DT,
as well as addds support for the magic reboot reason
values that are written to the address for each mode.
Cc: Rob Herring
Cc: Andy Gross
Cc: Bjorn Andersson
Cc:
This patch add the IMEM syscon memory region to the DT,
as well as addds support for the magic reboot reason
values that are written to the address for each mode.
Cc: Rob Herring
Cc: Andy Gross
Cc: Bjorn Andersson
Cc: Stephen Boyd
Cc: linux-arm-...@vger.kernel.org
Cc:
Most 8064 devices have micro-usb ports for phy1, so setting
the dr_mode to host here seems incorrect.
Leaving it unspecified should default to otg, and then
any boards that wish to specify something else, can
override it in their dts file.
Cc: Rob Herring
Cc: Andy Gross
Most 8064 devices have micro-usb ports for phy1, so setting
the dr_mode to host here seems incorrect.
Leaving it unspecified should default to otg, and then
any boards that wish to specify something else, can
override it in their dts file.
Cc: Rob Herring
Cc: Andy Gross
Cc: Bjorn Andersson
Hi Lars,
On Thu, Aug 04, 2016 at 12:21:08PM +0200, Lars-Peter Clausen wrote:
> And then also drop the if (!indio_dev->info) at the beginning of the function.
I was poking through the usage of this ->info field, and it looks like
it's supposed to be protected by the 'info_exist_lock' lock, but
Hi Lars,
On Thu, Aug 04, 2016 at 12:21:08PM +0200, Lars-Peter Clausen wrote:
> And then also drop the if (!indio_dev->info) at the beginning of the function.
I was poking through the usage of this ->info field, and it looks like
it's supposed to be protected by the 'info_exist_lock' lock, but
On Thu, 4 Aug 2016 00:47:27 -0400
David Long wrote:
> On 07/29/2016 05:01 AM, Daniel Thompson wrote:
> > On 28/07/16 15:40, Catalin Marinas wrote:
> >> On Wed, Jul 27, 2016 at 06:13:37PM -0400, David Long wrote:
> >>> On 07/27/2016 07:50 AM, Daniel Thompson wrote:
> On
On Thu, 4 Aug 2016 00:47:27 -0400
David Long wrote:
> On 07/29/2016 05:01 AM, Daniel Thompson wrote:
> > On 28/07/16 15:40, Catalin Marinas wrote:
> >> On Wed, Jul 27, 2016 at 06:13:37PM -0400, David Long wrote:
> >>> On 07/27/2016 07:50 AM, Daniel Thompson wrote:
> On 25/07/16 23:27, David
On 08/08/2016 01:31 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:32PM -0700, York Sun wrote:
>
> <--- Missing commit message.
>
>> Signed-off-by: York Sun
>>
>> ---
>> Change log
>> v3: no change
>> v2: no change
>>
>> drivers/edac/fsl_ddr_edac.c | 12
Hi Stephan,
On Mon, Aug 08, 2016 at 05:29:30PM +, Jason Cooper wrote:
> On Mon, Aug 08, 2016 at 08:41:36AM +0200, Stephan Mueller wrote:
...
> > If you think that this patch is a challenge because your driver starts to
> > spin, please help and offer another solution.
>
> Well, I don't buy
On 08/08/2016 01:31 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:32PM -0700, York Sun wrote:
>
> <--- Missing commit message.
>
>> Signed-off-by: York Sun
>>
>> ---
>> Change log
>> v3: no change
>> v2: no change
>>
>> drivers/edac/fsl_ddr_edac.c | 12 ++--
>>
Hi Stephan,
On Mon, Aug 08, 2016 at 05:29:30PM +, Jason Cooper wrote:
> On Mon, Aug 08, 2016 at 08:41:36AM +0200, Stephan Mueller wrote:
...
> > If you think that this patch is a challenge because your driver starts to
> > spin, please help and offer another solution.
>
> Well, I don't buy
Linus, Eric,
On Mon, 8 Aug 2016 14:19:23 -0700
Linus Torvalds wrote:
> On Mon, Aug 8, 2016 at 1:24 PM, Eric W. Biederman
> wrote:
> >
> > Booting up v4.8-rc1 in qemu today I ran I ran into this beautiful oops.
> >
> > I am just about to
Linus, Eric,
On Mon, 8 Aug 2016 14:19:23 -0700
Linus Torvalds wrote:
> On Mon, Aug 8, 2016 at 1:24 PM, Eric W. Biederman
> wrote:
> >
> > Booting up v4.8-rc1 in qemu today I ran I ran into this beautiful oops.
> >
> > I am just about to head out the door on vacation until the end of the
> >
Dmitry Torokhov writes:
> On Mon, Aug 8, 2016 at 2:08 PM, Eric W. Biederman
> wrote:
>> Dmitry Torokhov writes:
>>
>>> If net namespace is attached to a user namespace let's make container's
>>> root owner of sysctls
Dmitry Torokhov writes:
> On Mon, Aug 8, 2016 at 2:08 PM, Eric W. Biederman
> wrote:
>> Dmitry Torokhov writes:
>>
>>> If net namespace is attached to a user namespace let's make container's
>>> root owner of sysctls affecting said network namespace instead of global
>>> root.
>>>
>>> This
On Thu, Aug 4, 2016 at 8:22 PM, Dmitry Torokhov
wrote:
> There are certain parameters that belong to net namespace and that are
> exported in /proc. They should be controllable by the container's owner,
> but are currently owned by global root and thus not available.
>
On Thu, Aug 4, 2016 at 8:22 PM, Dmitry Torokhov
wrote:
> There are certain parameters that belong to net namespace and that are
> exported in /proc. They should be controllable by the container's owner,
> but are currently owned by global root and thus not available.
>
> Let's change proc code to
201 - 300 of 1814 matches
Mail list logo