From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the ftrace tree
Date: Thu, 11 Feb 2021 15:27:54 -0600 [thread overview]
Message-ID: <8477502be8c33e7d21f1c0facb3c1ad9e4257f90.camel@kernel.org> (raw)
In-Reply-To: <20210211162154.33d71924@gandalf.local.home>
On Thu, 2021-02-11 at 16:21 -0500, Steven Rostedt wrote:
> On Fri, 12 Feb 2021 07:57:28 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > In commit
> >
> > b5e7014fe1c4 ("selftests/ftrace: Update synthetic event syntax
> > errors")
> >
> > Fixes tag
> >
> > Fixes: 81ff92a93d95 (selftests/ftrace: Add test case for
> > synthetic
> >
> > has these problem(s):
> >
> > - Subject has leading but no trailing parentheses
> >
> > Please do not split Fixes tags over more than one line. Also, keep
> > all
> > the commit message tags together at the end of the message.
> >
>
> Thanks, I didn't even notice that :-/
>
> Tom, FYI for next time ;-)
>
Yep, thanks, Stephen, for pointing that out, didn't realize it until
now either.
Tom
> -- Steve
next prev parent reply other threads:[~2021-02-11 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 20:57 linux-next: Fixes tag needs some work in the ftrace tree Stephen Rothwell
2021-02-11 21:21 ` Steven Rostedt
2021-02-11 21:27 ` Tom Zanussi [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-17 21:35 Stephen Rothwell
2024-03-17 21:46 ` Steven Rostedt
2024-11-19 6:40 Stephen Rothwell
2024-11-19 14:00 ` Steven Rostedt
2025-03-24 2:35 Stephen Rothwell
2025-03-24 20:28 ` Steven Rostedt
2025-03-24 20:29 ` Steven Rostedt
2025-11-20 23:52 Stephen Rothwell
2025-11-21 9:12 ` Tomas Glozar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8477502be8c33e7d21f1c0facb3c1ad9e4257f90.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox