Hi,
On Tue, Jan 26, 2016 at 3:59 PM, Andrew Morton
wrote:
> On Mon, 11 Jan 2016 09:30:22 -0800 Douglas Anderson
> wrote:
>
>> This series of patches will speed up memory allocation in dma-mapping
>> quite a bit.
>
> This is pretty much all ARM and driver stuff so I think I'll duck it.
> But I c
On Mon, 11 Jan 2016 09:30:22 -0800 Douglas Anderson
wrote:
> This series of patches will speed up memory allocation in dma-mapping
> quite a bit.
This is pretty much all ARM and driver stuff so I think I'll duck it.
But I can merge it if nobody else feels a need to.
I saw a few acked-by/teste
Hello Doug,
On Mon, Jan 11, 2016 at 2:30 PM, Douglas Anderson wrote:
[snip]
>
> All testing was done on the chromeos kernel-3.8 and kernel-3.14.
> Sanity (compile / boot) testing was done on a v4.4-rc6-based kernel on
> rk3288, though the video codec isn't there. I don't have graphics / MFC
>
On Tue, Jan 26, 2016 at 10:27 AM, Andy Lutomirski wrote:
> On Tue, Jan 26, 2016 at 10:09 AM, Austin S. Hemmelgarn
> wrote:
>> On 2016-01-26 12:15, Serge Hallyn wrote:
>>>
>>> Quoting Josh Boyer (jwbo...@fedoraproject.org):
What you're saying is true for the "oh crap" case of a new userns
>>>
On Tue, Jan 26, 2016 at 9:15 AM, Serge Hallyn wrote:
> Quoting Josh Boyer (jwbo...@fedoraproject.org):
>> What you're saying is true for the "oh crap" case of a new userns
>> related CVE being found. However, there is the case where sysadmins
>> know for a fact that a set of machines should not a
On 2016-01-26 14:56, Josh Boyer wrote:
On Tue, Jan 26, 2016 at 12:20 PM, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
On Tue, Jan 26, 2016 at 9:46 AM, Austin S. Hemmelgarn
wrote:
On 2016-01-26 09:38, Josh Boyer wrote:
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederm
On Tue, Jan 26, 2016 at 12:20 PM, Serge Hallyn wrote:
> Quoting Josh Boyer (jwbo...@fedoraproject.org):
>> On Tue, Jan 26, 2016 at 9:46 AM, Austin S. Hemmelgarn
>> wrote:
>> > On 2016-01-26 09:38, Josh Boyer wrote:
>> >>
>> >> On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
>> >> wrote:
>> >
From: Ben Hutchings
perf_event_paranoid was only documented in source code and a perf error
message. Copy the documentation from the error message to
Documentation/sysctl/kernel.txt.
perf_cpu_time_max_percent was already documented but missing from the
list at the top, so add it there.
Signed-
Em Tue, Jan 26, 2016 at 10:08:21AM -0700, Mathieu Poirier escreveu:
> On 25 January 2016 at 14:29, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jan 25, 2016 at 06:12:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> >> Em Mon, Jan 25, 2016 at 01:46:22PM -0700, Mathieu Poirier escreveu:
> >> > On 14
On 2016-01-26 13:27, Andy Lutomirski wrote:
On Tue, Jan 26, 2016 at 10:09 AM, Austin S. Hemmelgarn
wrote:
On 2016-01-26 12:15, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
Kees Cook writes:
On Mon, Jan 2
On Tue, Jan 26, 2016 at 10:09 AM, Austin S. Hemmelgarn
wrote:
> On 2016-01-26 12:15, Serge Hallyn wrote:
>>
>> Quoting Josh Boyer (jwbo...@fedoraproject.org):
>>>
>>> On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
>>> wrote:
Kees Cook writes:
> On Mon, Jan 25, 2016 at 11:
On 2016-01-26 12:15, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
Kees Cook writes:
On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
wrote:
Kees Cook writes:
Well, I don't know about less weird, but it
Quoting Josh Boyer (jwbo...@fedoraproject.org):
> On Tue, Jan 26, 2016 at 9:46 AM, Austin S. Hemmelgarn
> wrote:
> > On 2016-01-26 09:38, Josh Boyer wrote:
> >>
> >> On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
> >> wrote:
> >>>
> >>> Kees Cook writes:
> >>>
> On Mon, Jan 25, 2016 at
Quoting Josh Boyer (jwbo...@fedoraproject.org):
> On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
> wrote:
> > Kees Cook writes:
> >
> >> On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
> >> wrote:
> >>> Kees Cook writes:
>
> Well, I don't know about less weird, but it would l
On 25 January 2016 at 14:29, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jan 25, 2016 at 06:12:42PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Jan 25, 2016 at 01:46:22PM -0700, Mathieu Poirier escreveu:
>> > On 14 January 2016 at 14:46, Mathieu Poirier
>> > wrote:
>> > > For memory alloc
Looks like the HPET spec at intel.com got moved.
Update the link.
Signed-off-by: Michael S. Tsirkin
---
drivers/char/hpet.c | 2 +-
Documentation/timers/hpet.txt | 2 +-
arch/x86/Kconfig | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/char/hp
On Mon, Jan 25, 2016 at 8:57 PM, Eric W. Biederman
wrote:
> Kees Cook writes:
>
>> On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
>> wrote:
>>> Kees Cook writes:
Well, I don't know about less weird, but it would leave a unneeded
hole in the permission checks.
>>>
>>> To be c
Looks like the VT-D spec at intel.com got moved.
Update the link.
Signed-off-by: Michael S. Tsirkin
---
Documentation/Intel-IOMMU.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/Intel-IOMMU.txt b/Documentation/Intel-IOMMU.txt
index 7b57fc0..49585b6 100644
--
Mathieu Poirier writes:
> Adding an ETB10 specific AUX area operations to be used
> by the perf framework when events are initialised.
>
> Part of this operation involves modeling the mmap'ed area
> based on the specific ways a sink buffer gathers information.
I don't mind being CC'd on the rest
Mathieu Poirier writes:
> +static int etm_event_init(struct perf_event *event)
> +{
> + if (event->attr.type != etm_pmu.type)
> + return -ENOENT;
> +
> + if (event->cpu >= nr_cpu_ids)
> + return -EINVAL;
perf_event_alloc() already does this. Except for this one do
On Tue, 26 Jan 2016 07:48:21 -0700
Jonathan Corbet wrote:
> For HTML-page splitting, we can see if the tools can help us, consider
> splitting the template files, or do the splitting in a postprocessing
> step. Docproc (or whatever replaces it) could also maybe do that work.
> It doesn't seem to
On Tue, Jan 26, 2016 at 9:46 AM, Austin S. Hemmelgarn
wrote:
> On 2016-01-26 09:38, Josh Boyer wrote:
>>
>> On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
>> wrote:
>>>
>>> Kees Cook writes:
>>>
On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
wrote:
>
> Kees Cook wri
On 2016-01-26 09:38, Josh Boyer wrote:
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
Kees Cook writes:
On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
wrote:
Kees Cook writes:
Well, I don't know about less weird, but it would leave a unneeded
hole in the permission chec
On Tue, 26 Jan 2016 14:08:45 +0200
Jani Nikula wrote:
> I'm afraid we've done some overlapping work in the mean time, but I'm
> happy we've both looked at the tool chain, and can have a more
> meaningful conversation now.
Overlapping work is just how this kernel thing works :)
> I first took ro
Hi Uwe,
On 01/26/2016 12:09 AM, Uwe Kleine-König wrote:
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:07PM -0800, Guenter Roeck wrote:
Patch #1 adds timer functionality to the watchdog core. It solves the problem
of short maximum hardware timeouts by augmenting heartbeats triggered from
user sp
Hi Uwe,
On 01/26/2016 12:07 AM, Uwe Kleine-König wrote:
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:11PM -0800, Guenter Roeck wrote:
From: Guenter Roeck
Some watchdogs require a minimum time between heartbeats.
Examples are the watchdogs in DA9062 and AT91SAM9x.
Signed-off-by: Guenter Roec
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
> Kees Cook writes:
>
>> On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
>> wrote:
>>> Kees Cook writes:
Well, I don't know about less weird, but it would leave a unneeded
hole in the permission checks.
>>>
>>> To be
On Tue, 26 Jan 2016, Daniel Vetter wrote:
> On Tue, Jan 26, 2016 at 1:08 PM, Jani Nikula wrote:
>> I first took roughly the same approach as you did. I was really
>> impressed with the speed and the beauty of the produced HTML. The
>> trouble is, neither asciidoc nor asciidoctor can produce chunk
On Tue, Jan 26, 2016 at 1:08 PM, Jani Nikula wrote:
> On Tue, 26 Jan 2016, Jonathan Corbet wrote:
>> So here is a proof-of-concept series showing how a fully asciidoc-based
>> toolchain might work. Lots of hackery here, this isn't meant to be applied
>> to anything at this point, but it's a good
Instead of having the kernel-doc usage in both comments and in output to
the user, merge them all to one here document. While at it, imrove the
text and make it pretty. Give shoemaker's children some shoes.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 83 --
On Tue, 26 Jan 2016, Jonathan Corbet wrote:
> So here is a proof-of-concept series showing how a fully asciidoc-based
> toolchain might work. Lots of hackery here, this isn't meant to be applied
> to anything at this point, but it's a good start. What this series has is:
>
> - Jani Nikula's pat
Add new -asciidoc option to produce asciidoc output from kernel-doc. The
output is formatted internally, with no dependencies on external
tools. Any asciidoc formatting present in kernel-doc will naturally be
present in the resulting asciidoc as well.
Highlighting of functions(), &struct structure
Given a list of special format filenames, generate dependencies and
rules for kernel-doc invocation on those files, to be included in to
Makefiles.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc-deps | 66 +
1 file changed, 66 insertions(+)
cre
Given an asciidoc input file in standard input, print the files included
using asciidoc include macros to standard output, one per line. This
will be helpful in asciidoc dependency generation.
Signed-off-by: Jani Nikula
---
scripts/asciidoc-includes | 6 ++
1 file changed, 6 insertions(+)
c
Use some pre- and post-processing to handle the "![EIFPCD]" docproc
directives in the DocBook, and let pandoc do the rest. Manual editing
will be required, but this will give a big jump start.
The asciidoc result would be nicer without the pandoc --no-wrap option,
but unfortunately pandoc also wra
-function supports printing named DOC: sections, but spaces and braces
and quotes etc. are allowed in section titles. This is tricky to handle
in scripts, let alone Makefiles.
Add a new -doc parameter for dumping doc sections (to not convolute
-function more than it already is), with support for "
Add a helper for calling kernel-doc, with the -w parameter describing
the parameters to pass on to kernel-doc, in a special format.
[This is easier to explain and will make more sense in the context of
the following patches. The -w parameter is expected to be a filename
with the kernel-doc paramet
Currently we use docproc to figure out which symbols are exported, and
then docproc calls kernel-doc on specific functions, to get
documentation on exported functions. According to git blame and docproc
comments, this is due to historical reasons, as functions and their
corresponding EXPORT_SYMBOL*
Finally wrap up all the work in the preceding patches, and generate a
pipeline from asciidoc documentation as part of the DocBook
documentation.
The biggest difference in building DocBook xml from asciidoc compared to
the docproc pipeline is the use of intermediate asciidoc snippets for
the kernel
This is the verbatim result of
$ scripts/tmpl2asciidoc < Documentation/DocBook/gpu.tmpl >
Documentation/DocBook/gpu.txt
$ rm Documentation/DocBook/gpu.tmpl
It should probably be split up to separate documents for GPU drivers
etc. using include macros within asciidoc, but this is for demonstratio
On Tue, 26 Jan 2016, Jonathan Corbet wrote:
> On Mon, 18 Jan 2016 10:41:17 +0200
> Jani Nikula wrote:
>
>> Add new -asciidoc option to produce asciidoc output from kernel-doc. The
>> output is formatted internally, with no dependencies on external
>> tools. Any asciidoc formatting present in kern
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:07PM -0800, Guenter Roeck wrote:
> Patch #1 adds timer functionality to the watchdog core. It solves the problem
> of short maximum hardware timeouts by augmenting heartbeats triggered from
> user space with internally triggered heartbeats.
>
> Patch #
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:11PM -0800, Guenter Roeck wrote:
> From: Guenter Roeck
>
> Some watchdogs require a minimum time between heartbeats.
> Examples are the watchdogs in DA9062 and AT91SAM9x.
>
> Signed-off-by: Guenter Roeck
> ---
> v7: Rebased to v4.5-rc1
> v6: Rebased
43 matches
Mail list logo
