linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>
Cc: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the risc-v-fixes tree
Date: Tue, 26 Apr 2022 08:01:02 +1000	[thread overview]
Message-ID: <20220426080102.7263b1ad@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 505 bytes --]

Hi all,

In commit

  760d10a5b792 ("RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL")

Fixes tag

  Fixes: 617d32938d1b ("rpmsg: Move the rpmsg control device from rpmsg_char to rpmsg_ctrl", 2022-01-24)

has these problem(s):

  - Subject has leading but no trailing quotes
  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

Please do not add the date field, it doesn't add anything.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-04-25 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 22:01 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-01 23:12 linux-next: Fixes tag needs some work in the risc-v-fixes tree Stephen Rothwell
2023-06-02  1:27 ` Palmer Dabbelt
2020-09-30 12:41 Stephen Rothwell
2020-03-19  8:06 Stephen Rothwell
2020-03-19 10:04 ` Greentime Hu

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=20220426080102.7263b1ad@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    /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;
as well as URLs for NNTP newsgroup(s).