Am Dienstag, 13. Dezember 2016, 16:40:01 CET schrieb Jonathan Corbet:
Hi Jonathan,
> Clearly there was a bit of misunderstanding going around :)
Yep, it seems like it :-)
>
> I've applied the patch set to docs-next. Oddly I had no trouble with #7,
> but #2 was badly mailer-mangled and took som
On Wed, 2016-12-14 at 00:37 +, Nicholas Mc Guire wrote:
> On Tue, Dec 13, 2016 at 04:27:32PM -0800, Joe Perches wrote:
> > a, On Tue, 2016-12-13 at 09:19 +, Nicholas Mc Guire wrote:
> > > On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > > > On Tue, 13 Dec 2016, Nicholas Mc G
On 12/14/2016 at 11:08 AM, Xunlei Pang wrote:
> On 12/10/2016 at 01:20 PM, Robert LeBlanc wrote:
>> On Fri, Dec 9, 2016 at 7:49 PM, Baoquan He wrote:
>>> On 12/09/16 at 05:22pm, Robert LeBlanc wrote:
When trying to configure crashkernel greater than about 800 MB, the
kernel fails to allo
On 12/10/2016 at 01:20 PM, Robert LeBlanc wrote:
> On Fri, Dec 9, 2016 at 7:49 PM, Baoquan He wrote:
>> On 12/09/16 at 05:22pm, Robert LeBlanc wrote:
>>> When trying to configure crashkernel greater than about 800 MB, the
>>> kernel fails to allocate memory on x86 and x86_64. This is due to an
>>>
On Fri, Dec 09, 2016 at 05:50:17PM +1100, Andrew Donnellan wrote:
>On 09/12/16 17:24, Linas Vepstas wrote:
>>I suppose I'm confused, but I recall that link resets are non-fatal.
>>Fatal errors typically require that the the pci adapter be completely
>>reset, any adapter firmware to be reloaded from
On Tue, Dec 13, 2016 at 04:27:32PM -0800, Joe Perches wrote:
> a, On Tue, 2016-12-13 at 09:19 +, Nicholas Mc Guire wrote:
> > On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > > useleep_range() with a delta of 0 makes no sens
a, On Tue, 2016-12-13 at 09:19 +, Nicholas Mc Guire wrote:
> On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > useleep_range() with a delta of 0 makes no sense and only prevents the
> > > timer subsystem from optimizing interru
On Tue, 13 Dec 2016 16:20:59 +0100
Dmitry Vyukov wrote:
> Now that we have gcc plugins and in particular sancov plugin,
> KCOV can be used with gcc 4.5+. Note this in the docs.
Makes sense. Applied to docs-next, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc
On Tue, 13 Dec 2016 15:40:57 +0100
Hans Holmberg wrote:
> A bunch of documentation files have moved, correct the paths.
Good catch. Guess I'm as good a messenger as anybody else for this one;
applied to docs-next, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-d
On Tue, 13 Dec 2016 23:06:14 +0100
Stephan Müller wrote:
> I am sorry, then I may have misunderstood you.
>
> I would think that Herbert agreed that you push the entire patch set through
> your tree, including the documentation changes to the crypto header files.
>
> I just did a patch on the
Am Dienstag, 13. Dezember 2016, 14:50:59 CET schrieb Jonathan Corbet:
Hi Jonathan,
> On Tue, 13 Dec 2016 22:25:07 +0100
>
> Stephan Müller wrote:
> > Considering that a large batch of documentation updates just landed in
> > Linus' tree, I am wondering why the crypto API documentation update is
On Tue, 13 Dec 2016 22:25:07 +0100
Stephan Müller wrote:
> Considering that a large batch of documentation updates just landed in Linus'
> tree, I am wondering why the crypto API documentation update is not among it.
Well, I'd asked if I could run the documentation-specific parts through
docs-n
Am Dienstag, 25. Oktober 2016, 10:35:49 CET schrieb Herbert Xu:
Hi Jonathan,
> > > > the attached patch set converts the existing crypto API documentation
> > > > from DocBook to Sphinx.
> > >
> > > This looks generally good to me - thanks for doing it!
> > >
> > > Is there any chance of runnin
t; > +++ b/tools/testing/selftests/kmod/kmod.sh
> > @@ -0,0 +1,449 @@
> > +#!/bin/bash
> > +#
<-- snip -->
> > +# You'll want at least 4096 GiB of RAM to expect to run these tests
>
> 4TiB of RAM? I assume this was meant to be 4 GiB not 4096?
Whoops, ye
On Tue, Dec 13, 2016 at 10:16:23AM +, Hui Chun Ong wrote:
> On Sat, 2016-12-10 at 09:22 -0800, Guenter Roeck wrote:
> > On 12/10/2016 02:25 AM, Hui Chun Ong wrote:
> > >
> > > Add support for the watchdog timer on PXI Embedded Controller.
> > >
> > > Signed-off-by: Hui Chun Ong
> > > ---
> >
On 12/13/2016 05:13 PM, Dmitry Vyukov wrote:
> On Tue, Dec 13, 2016 at 2:59 PM, Andrey Ryabinin
> wrote:
>> On 12/13/2016 12:38 PM, Dmitry Vyukov wrote:
>>> On Tue, Dec 13, 2016 at 10:20 AM, Andrey Ryabinin
>>> wrote:
On 12/13/2016 11:58 AM, Dmitry Vyukov wrote:
> --- a/
Now that we have gcc plugins and in particular sancov plugin,
KCOV can be used with gcc 4.5+. Note this in the docs.
I've tested CONFIG_KCOV with gcc 4.8.4 (stock for ubuntu 14.04)
and it works. It even emits very comparable number of coverage
callbacks: 420153 vs 422211 for gcc 7.0.
Cc: Jonathan
A bunch of documentation files have moved, correct the paths.
Signed-off-by: Hans Holmberg
---
lib/Kconfig.debug | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index e6327d1..18ffa80 100644
--- a/lib/Kconfig.debug
++
On Tue, Dec 13, 2016 at 2:59 PM, Andrey Ryabinin
wrote:
> On 12/13/2016 12:38 PM, Dmitry Vyukov wrote:
>> On Tue, Dec 13, 2016 at 10:20 AM, Andrey Ryabinin
>> wrote:
>>>
>>>
>>> On 12/13/2016 11:58 AM, Dmitry Vyukov wrote:
>>>
--- a/Documentation/dev-tools/kasan.rst
+++ b/Documentation/
On 12/13/2016 12:38 PM, Dmitry Vyukov wrote:
> On Tue, Dec 13, 2016 at 10:20 AM, Andrey Ryabinin
> wrote:
>>
>>
>> On 12/13/2016 11:58 AM, Dmitry Vyukov wrote:
>>
>>> --- a/Documentation/dev-tools/kasan.rst
>>> +++ b/Documentation/dev-tools/kasan.rst
>>> @@ -40,6 +40,14 @@ similar to the following
Thanks Jonathan!
On 12 December 2016 at 01:14, Jonathan Corbet wrote:
> On Sun, 11 Dec 2016 18:35:42 +0100
> Daniel Vetter wrote:
>
>> > Here's a thought, though: how about if we slip in a little version of
>> > dma-buf.rst now with a "coming soon, don't miss it!!" message? Then the
>> > rest o
On Tue, Dec 13, 2016 at 01:05:12PM +0100, Julia Lawall wrote:
>
>
> On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
>
> > On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > > useleep_range() with a delta of 0 makes no sense and o
On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > useleep_range() with a delta of 0 makes no sense and only prevents the
> > > timer subsystem from optimizing interrupts. As any us
On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> I fully agree - without automation it is almost usless
> the coccinelle spatch is a seperate patch and it is tested butnot yet
> submitted.
Good, good! Sorry for the noise.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
--
To unsu
On Sat, 2016-12-10 at 09:22 -0800, Guenter Roeck wrote:
> On 12/10/2016 02:25 AM, Hui Chun Ong wrote:
> >
> > Add support for the watchdog timer on PXI Embedded Controller.
> >
> > Signed-off-by: Hui Chun Ong
> > ---
> > v2: Remove mutex lock and platform_device *pdev fields from struct
> > nic7
On Tue, Dec 13, 2016 at 10:20 AM, Andrey Ryabinin
wrote:
>
>
> On 12/13/2016 11:58 AM, Dmitry Vyukov wrote:
>
>> --- a/Documentation/dev-tools/kasan.rst
>> +++ b/Documentation/dev-tools/kasan.rst
>> @@ -40,6 +40,14 @@ similar to the following to the respective kernel
>> Makefile:
>>
>> KASAN
Em Mon, 12 Dec 2016 12:56:50 -0800
Joe Perches escreveu:
> On Mon, 2016-12-12 at 11:00 -0700, Jonathan Corbet wrote:
> > On Fri, 2 Dec 2016 10:15:13 -0200
> > Mauro Carvalho Chehab wrote:
> >
> > > On the past approaches, was planning to keep the documentation
> > > about what's at the MAINT
On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > useleep_range() with a delta of 0 makes no sense and only prevents the
> > timer subsystem from optimizing interrupts. As any user of usleep_range()
> > is in non-atomic context the tim
On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> useleep_range() with a delta of 0 makes no sense and only prevents the
> timer subsystem from optimizing interrupts. As any user of usleep_range()
> is in non-atomic context the timer jitter is in the range of 10s of
> microseconds anyway.
>
> This
On Tue, Dec 13, 2016 at 6:57 AM, Maninder Singh wrote:
> This provide option to control sanity of read and write operations
> Both read and write instrumentation increase size of uImage, So using
> this option read or write instrumentation can be avoided if not required.
> Useful in case of module
30 matches
Mail list logo
