From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
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 mm-hotfixes tree
Date: Wed, 3 Jul 2024 08:09:29 +1000 [thread overview]
Message-ID: <20240703080929.319d3e52@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Hi all,
In commit
e968e6d21d03 ("lib/build_OID_registry: avoid non-destructive substitution for Perl < 5.13.2 compat")
Fixes tag
Fixes: 5ef6dc08cfde ("lib/build_OID_registry: don't mention the full path of
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-02 22:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 22:09 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-09 4:08 linux-next: Fixes tag needs some work in the mm-hotfixes tree Stephen Rothwell
2025-09-10 7:32 Stephen Rothwell
2025-08-26 9:08 Stephen Rothwell
2025-08-20 4:50 Stephen Rothwell
2025-08-12 6:44 Stephen Rothwell
2025-08-12 13:46 ` Pasha Tatashin
2025-08-12 20:12 ` Andrew Morton
2024-10-07 20:44 Stephen Rothwell
2024-08-25 21:26 Stephen Rothwell
2024-08-04 21:17 Stephen Rothwell
2024-08-05 2:47 ` Muchun Song
2023-11-29 20:43 Stephen Rothwell
2023-11-30 1:07 ` Baoquan He
2023-06-07 4:35 Stephen Rothwell
2022-08-07 21:19 Stephen Rothwell
2022-08-07 23:01 ` Peter Xu
2022-04-27 22: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=20240703080929.319d3e52@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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