From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
James Hogan <jhogan@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the mips-fixes tree
Date: Thu, 27 Feb 2020 15:02:11 +0100 [thread overview]
Message-ID: <20200227140211.GA17887@alpha.franken.de> (raw)
In-Reply-To: <1582811024.3.0@crapouillou.net>
On Thu, Feb 27, 2020 at 10:43:44AM -0300, Paul Cercueil wrote:
> Le jeu., févr. 27, 2020 at 07:17, Stephen Rothwell <sfr@canb.auug.org.au> a
> écrit :
> >Hi all,
> >
> >In commit
> >
> > 3944dee0c6cd ("MIPS: Fix CONFIG_MIPS_CMDLINE_DTB_EXTEND handling")
> >
> >Fixes tag
> >
> > Fixes: 7784cac69735 ("MIPS: cmdline: Clean up boot_command_line
> >
> >has these problem(s):
> >
> > - Subject has leading but no trailing parentheses
> > - Subject has leading but no trailing quotes
> >
> >Please do not split Fixes tags over more than one line.
>
> My fault, sorry. I did not know they could not be splitted.
I've fixed it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-02-27 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 20:17 linux-next: Fixes tag needs some work in the mips-fixes tree Stephen Rothwell
2020-02-27 13:43 ` Paul Cercueil
2020-02-27 14:02 ` Thomas Bogendoerfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-03 8:42 Stephen Rothwell
2020-09-03 10:01 ` Thomas Bogendoerfer
2020-02-19 20:36 Stephen Rothwell
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=20200227140211.GA17887@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul@crapouillou.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.