On Mon, 16 Nov 2020 13:29:29 -0700
Jonathan Corbet wrote:
> > Would something like the below work? I think I fixed the other places with
> > issues and for consistency, replaced the ".. code-block:: c" with just "::"
> > usage throughout the file.
>
> That will work. It will also have the eff
On Mon, 16 Nov 2020 15:25:52 -0500
Steven Rostedt wrote:
> On Mon, 16 Nov 2020 12:24:32 -0700
> Jonathan Corbet wrote:
>
> > The problem is those literal blocks. The easiest fix will be to just use
> > the double-colon notation to indicate a literal block, so the paragraph
> > above would end
On Mon, 16 Nov 2020 12:24:32 -0700
Jonathan Corbet wrote:
> The problem is those literal blocks. The easiest fix will be to just use
> the double-colon notation to indicate a literal block, so the paragraph
> above would end with "...start your code with::". Note that there's a few
> of them to
On Mon, 16 Nov 2020 12:43:38 -0500
Steven Rostedt wrote:
> > After merging the ftrace tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/trace/ftrace-uses.rst:123: WARNING: Unexpected indentation.
> >
> > Introduced by commit
> >
> > a25d036d939a ("ftr
On Mon, 16 Nov 2020 17:35:02 +1100
Stephen Rothwell wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/trace/ftrace-uses.rst:123: WARNING: Unexpected indentation.
>
> Introduced by commit
>
> a25d036d939a ("ftra
Hi all,
After merging the ftrace tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/trace/ftrace-uses.rst:123: WARNING: Unexpected indentation.
Introduced by commit
a25d036d939a ("ftrace: Reverse what the RECURSION flag means in the
ftrace_ops")
--
Cheers,
Steph
On Wed, 5 Aug 2020 12:53:39 +0800
Muchun Song wrote:
> On Wed, Aug 5, 2020 at 12:21 PM Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > After merging the ftrace tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced this warning:
> >
> > kernel/kprobes.c: In function 'kill_kprob
On Wed, Aug 5, 2020 at 11:11 PM Steven Rostedt wrote:
>
> On Wed, 5 Aug 2020 12:53:39 +0800
> Muchun Song wrote:
>
> > On Wed, Aug 5, 2020 at 12:21 PM Stephen Rothwell
> > wrote:
> > >
> > > Hi all,
> > >
> > > After merging the ftrace tree, today's linux-next build (powerpc
> > > ppc64_defconf
On Thu, 6 Aug 2020 02:04:45 +0900
Masami Hiramatsu wrote:
> > Looks like that would work. Care to send a formal patch. Could you also
> > change arm_kprobe_ftrace() as well?
>
> Looks good to me too as far as updating it to static inline function.
Can you add an Acked-by to the final patch fr
On Wed, 5 Aug 2020 11:11:05 -0400
Steven Rostedt wrote:
> On Wed, 5 Aug 2020 12:53:39 +0800
> Muchun Song wrote:
>
> > On Wed, Aug 5, 2020 at 12:21 PM Stephen Rothwell
> > wrote:
> > >
> > > Hi all,
> > >
> > > After merging the ftrace tree, today's linux-next build (powerpc
> > > ppc64_defco
On Wed, Aug 5, 2020 at 12:21 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> kernel/kprobes.c: In function 'kill_kprobe':
> kernel/kprobes.c:1116:33: warning: statement with no effect [-Wunuse
Hi all,
After merging the ftrace tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
kernel/kprobes.c: In function 'kill_kprobe':
kernel/kprobes.c:1116:33: warning: statement with no effect [-Wunused-value]
1116 | #define disarm_kprobe_ftrace(p) (-ENODEV)
|
On Wed, Jun 04, 2014 at 11:13:51PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 11:03:34 +0800
> Fengguang Wu wrote:
>
> > On Wed, Jun 04, 2014 at 10:36:24PM -0400, Steven Rostedt wrote:
> > > On Thu, 5 Jun 2014 10:14:57 +0800
> > > Fengguang Wu wrote:
> > >
> > > > > I wonder if the "(Red
On Thu, 5 Jun 2014 11:03:34 +0800
Fengguang Wu wrote:
> On Wed, Jun 04, 2014 at 10:36:24PM -0400, Steven Rostedt wrote:
> > On Thu, 5 Jun 2014 10:14:57 +0800
> > Fengguang Wu wrote:
> >
> > > > I wonder if the "(Red Hat)" part is causing an issue. Can you send
> > > > directly to my email "rost
On Wed, Jun 04, 2014 at 10:36:24PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 10:14:57 +0800
> Fengguang Wu wrote:
>
> > > I wonder if the "(Red Hat)" part is causing an issue. Can you send
> > > directly to my email "rost...@goodmis.org" and strip the name part?
> >
> > OK. I've committe
On Wed, Jun 04, 2014 at 10:36:24PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 10:14:57 +0800
> Fengguang Wu wrote:
>
> > > I wonder if the "(Red Hat)" part is causing an issue. Can you send
> > > directly to my email "rost...@goodmis.org" and strip the name part?
> >
> > OK. I've committe
On Thu, 5 Jun 2014 10:14:57 +0800
Fengguang Wu wrote:
> On Wed, Jun 04, 2014 at 09:39:32PM -0400, Steven Rostedt wrote:
> > On Thu, 5 Jun 2014 09:33:00 +0800
> > Fengguang Wu wrote:
> >
> >
> > > Here are the recent emails sent to you:
> > >
> > > 439 F May 10 To Steven Rostedt (4440:1) [t
On Wed, Jun 04, 2014 at 10:38:17PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 10:14:57 +0800
> Fengguang Wu wrote:
>
> > On Wed, Jun 04, 2014 at 09:39:32PM -0400, Steven Rostedt wrote:
> > > On Thu, 5 Jun 2014 09:33:00 +0800
> > > Fengguang Wu wrote:
> > >
> > >
> > > > Here are the rec
On Thu, 5 Jun 2014 10:14:57 +0800
Fengguang Wu wrote:
> On Wed, Jun 04, 2014 at 09:39:32PM -0400, Steven Rostedt wrote:
> > On Thu, 5 Jun 2014 09:33:00 +0800
> > Fengguang Wu wrote:
> >
> >
> > > Here are the recent emails sent to you:
> > >
> > > 439 F May 10 To Steven Rostedt (4440:1) [t
On Thu, 5 Jun 2014 10:14:57 +0800
Fengguang Wu wrote:
> > I wonder if the "(Red Hat)" part is causing an issue. Can you send
> > directly to my email "rost...@goodmis.org" and strip the name part?
>
> OK. I've committed the change. Let's see how well it will work.
OK, I never received an error
On Wed, Jun 04, 2014 at 09:39:32PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 09:33:00 +0800
> Fengguang Wu wrote:
>
>
> > Here are the recent emails sent to you:
> >
> > 439 F May 10 To Steven Rostedt (4440:1) [trace:ftrace/next-3.17 29/29]
> > kernel/trace/ftrace.c:108:27: warning:
On Thu, 5 Jun 2014 09:33:00 +0800
Fengguang Wu wrote:
> Here are the recent emails sent to you:
>
> 439 F May 10 To Steven Rostedt (4440:1) [trace:ftrace/next-3.17 29/29]
> kernel/trace/ftrace.c:108:27: warning: 'removed_ops' defined but not used
> 446 F May 10 To Steven Rostedt (3531:1)
On Wed, Jun 04, 2014 at 09:12:02PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 09:03:53 +0800
> Fengguang Wu wrote:
>
> > > Was I Cc'd? I don't have that in my inbox, nor do I see it in any of my
> > > spam filters.
> >
> > Yes, here is the email message:
> >
> > Date: Sat, 31 May 20
On Wed, 4 Jun 2014 21:12:02 -0400
Steven Rostedt wrote:
> I may add a bad commit to one of my branches and see if I get a
> response from you just to test it out. I really hope we can fix this
> because I've gotten someone dependent on your reports. :-/
I did just this. I created a branch calle
On Thu, 5 Jun 2014 09:03:53 +0800
Fengguang Wu wrote:
> > Was I Cc'd? I don't have that in my inbox, nor do I see it in any of my
> > spam filters.
>
> Yes, here is the email message:
>
> Date: Sat, 31 May 2014 02:16:43 +0800
> From: kbuild test robot
> ==> To: "Steven Rost
On Wed, Jun 04, 2014 at 09:00:16PM -0400, Steven Rostedt wrote:
> On Thu, 5 Jun 2014 08:20:12 +0800
> Fengguang Wu wrote:
>
> > On Wed, Jun 04, 2014 at 12:26:12PM -0400, Steven Rostedt wrote:
> > > On Wed, 4 Jun 2014 16:09:21 +1000
> > > Stephen Rothwell wrote:
> > >
> > > > Hi Steven,
> > > >
On Thu, 5 Jun 2014 08:20:12 +0800
Fengguang Wu wrote:
> On Wed, Jun 04, 2014 at 12:26:12PM -0400, Steven Rostedt wrote:
> > On Wed, 4 Jun 2014 16:09:21 +1000
> > Stephen Rothwell wrote:
> >
> > > Hi Steven,
> > >
> > > After merging the ftrace tree, today's linux-next build (x86_64
> > > allm
On Wed, Jun 04, 2014 at 12:26:12PM -0400, Steven Rostedt wrote:
> On Wed, 4 Jun 2014 16:09:21 +1000
> Stephen Rothwell wrote:
>
> > Hi Steven,
> >
> > After merging the ftrace tree, today's linux-next build (x86_64
> > allmodconfig)
> > produced this warning:
> >
> > kernel/trace/trace_benchma
Hi Steve,
On Wed, 4 Jun 2014 12:26:12 -0400 Steven Rostedt wrote:
>
> On Wed, 4 Jun 2014 16:09:21 +1000
> Stephen Rothwell wrote:
>
> > After merging the ftrace tree, today's linux-next build (x86_64
> > allmodconfig)
> > produced this warning:
> >
> > kernel/trace/trace_benchmark.c: In funct
On Wed, 4 Jun 2014 16:09:21 +1000
Stephen Rothwell wrote:
> Hi Steven,
>
> After merging the ftrace tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> kernel/trace/trace_benchmark.c: In function 'trace_do_benchmark':
> kernel/trace/trace_benchmark.c:38:6: warning:
Hi Steven,
After merging the ftrace tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
kernel/trace/trace_benchmark.c: In function 'trace_do_benchmark':
kernel/trace/trace_benchmark.c:38:6: warning: unused variable 'seedsq'
[-Wunused-variable]
u64 seedsq;
^
Intr
31 matches
Mail list logo
