From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt•com>,
Paul Walmsley <paul.walmsley@sifive•com>
Cc: Changbin Du <changbin.du@gmail•com>,
Alexandre Ghiti <alex@ghiti•fr>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tags needs some work in the risc-v-fixes tree
Date: Thu, 12 Aug 2021 22:30:06 +1000 [thread overview]
Message-ID: <20210812223006.642bb3a3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Hi all,
In commit
007666bcc606 ("riscv: Fix comment regarding kernel mapping overlapping with IS_ERR_VALUE")
Fixes tag
Fixes: db6b84a368b4 ("riscv: Make sure the kernel mapping does not
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.
In commit
589be135381f ("riscv: kexec: do not add '-mno-relax' flag if compiler doesn't support it")
Fixes tag
Fixes: fba8a8674f ("RISC-V: Add kexec support")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-08-12 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 12:30 Stephen Rothwell [this message]
2021-08-12 14:17 ` linux-next: Fixes tags needs some work in the risc-v-fixes tree Palmer Dabbelt
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=20210812223006.642bb3a3@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alex@ghiti$(echo .)fr \
--cc=changbin.du@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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