Hi Steven,
On Wed, 3 Jun 2020 11:30:58 -0400 Steven Rostedt wrote:
>
> On Wed, 03 Jun 2020 10:24:36 -0500
> Tom Zanussi wrote:
>
> > > It appears to be the ascii art that is causing the issue. I have no
> > > idea
> > > how to fix it. If someone has a patch they would like to submit, I
> > > wi
On Wed, 03 Jun 2020 10:24:36 -0500
Tom Zanussi wrote:
> > It appears to be the ascii art that is causing the issue. I have no
> > idea
> > how to fix it. If someone has a patch they would like to submit, I
> > will
> > take it before I push it off to Linus.
> >
> > -- Steve
>
> I just sent yo
Hi Steve,
On Wed, 2020-06-03 at 11:22 -0400, Steven Rostedt wrote:
> On Wed, 3 Jun 2020 17:42:53 +1000
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the ftrace tree, today's linux-next build (htmldocs)
> > failed like this:
> >
> >
> > Sphinx parallel build error:
> > docutils
On Wed, 3 Jun 2020 17:42:53 +1000
Stephen Rothwell wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (htmldocs)
> failed like this:
>
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage:
> /home/sfr/next/next/Documentation/trace/histogram-design.rst:219:
Hi,
On Wed, 2020-06-03 at 17:42 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (htmldocs)
> failed like this:
>
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage:
> /home/sfr/next/next/Documentation/trace/histogram-design.rst:2
Hi all,
After merging the ftrace tree, today's linux-next build (htmldocs)
failed like this:
Sphinx parallel build error:
docutils.utils.SystemMessage:
/home/sfr/next/next/Documentation/trace/histogram-design.rst:219: (SEVERE/4)
Unexpected section title.
.
.
Caused by commit
16b585fe7192
On Fri, 21 Nov 2014 09:20:36 -0500
Steven Rostedt wrote:
> > diff --git a/include/linux/percpu.h b/include/linux/percpu.h
> > index a3aa63e..c94c766 100644
> > --- a/include/linux/percpu.h
> > +++ b/include/linux/percpu.h
> > @@ -7,6 +7,7 @@
> > #include
> > #include
> > #include
> > +#inc
On Fri, 21 Nov 2014, Steven Rostedt wrote:
> > From: Jiri Kosina
> > Subject: [PATCH] printk: make sure printk_func_t is known in percpu.h
> >
> > Commit afdc34a3d3b8 ("printk: Add per_cpu printk func to allow printk to
> > be diverted") caused percpu variable printk_func to be declared in
> >
>
> From: Jiri Kosina
> Subject: [PATCH] printk: make sure printk_func_t is known in percpu.h
>
> Commit afdc34a3d3b8 ("printk: Add per_cpu printk func to allow printk to
> be diverted") caused percpu variable printk_func to be declared in
> percpu.h. Make sure that the corresponding type is
On Fri, 21 Nov 2014 18:32:15 +1100
Stephen Rothwell wrote:
> Hi Steven,
>
> After merging the ftrace tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
>
> In file included from include/asm-generic/percpu.h:6:0,
> from arch/powerpc/include/asm/percpu.h:19,
On Fri, 21 Nov 2014, Stephen Rothwell wrote:
> Hi Steven,
>
> After merging the ftrace tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
>
> In file included from include/asm-generic/percpu.h:6:0,
> from arch/powerpc/include/asm/percpu.h:19,
>
Hi Steven,
After merging the ftrace tree, today's linux-next build (powerpc
allnoconfig) failed like this:
In file included from include/asm-generic/percpu.h:6:0,
from arch/powerpc/include/asm/percpu.h:19,
from include/linux/percpu.h:11,
from inc
Hi Steve,
On Fri, 01 Mar 2013 23:22:58 -0500 Steven Rostedt wrote:
>
> On Sat, 2013-03-02 at 15:17 +1100, Stephen Rothwell wrote:
> >
> > > I made some major changes and wanted testing on it as soon as possible.
> > > I've done tons of testing on my own but I wanted a broader audience. Do
> > >
On Sat, 2013-03-02 at 15:17 +1100, Stephen Rothwell wrote:
>
> > I made some major changes and wanted testing on it as soon as possible.
> > I've done tons of testing on my own but I wanted a broader audience. Do
> > you want me to pull my tree and reset it to what is only for 3.9?
>
> Yes, plea
Hi Steve,
On Fri, 01 Mar 2013 22:55:29 -0500 Steven Rostedt wrote:
>
> Oh crap, sorry. Quite the contrary. I should have waited for -rc1 as
> this is intended for v3.10.
>
> I made some major changes and wanted testing on it as soon as possible.
> I've done tons of testing on my own but I wanted
On Sat, 2013-03-02 at 14:42 +1100, Stephen Rothwell wrote:
> Hi Steve,
>
> On Fri, 01 Mar 2013 21:45:18 -0500 Steven Rostedt wrote:
> >
> > On Fri, 2013-03-01 at 13:47 +1100, Stephen Rothwell wrote:
> > >
> > > After merging the ftrace tree, today's linux-next build (x86_64
> > > allmodconfig) f
Hi Steve,
On Fri, 01 Mar 2013 21:45:18 -0500 Steven Rostedt wrote:
>
> On Fri, 2013-03-01 at 13:47 +1100, Stephen Rothwell wrote:
> >
> > After merging the ftrace tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > kernel/trace/trace_kdb.c: In function 'ftrace_dum
On Fri, 2013-03-01 at 13:47 +1100, Stephen Rothwell wrote:
> Hi Steven,
>
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/trace/trace_kdb.c: In function 'ftrace_dump_buf':
> kernel/trace/trace_kdb.c:29:33: error: invalid type argument
On Fri, 2013-03-01 at 13:47 +1100, Stephen Rothwell wrote:
> Hi Steven,
>
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/trace/trace_kdb.c: In function 'ftrace_dump_buf':
> kernel/trace/trace_kdb.c:29:33: error: invalid type argument
Hi Steven,
After merging the ftrace tree, today's linux-next build (x86_64
allmodconfig) failed like this:
kernel/trace/trace_kdb.c: In function 'ftrace_dump_buf':
kernel/trace/trace_kdb.c:29:33: error: invalid type argument of '->' (have
'struct trace_array_cpu')
kernel/trace/trace_kdb.c:86:33:
20 matches
Mail list logo
