From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Luis Chamberlain <mcgrof@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the modules tree
Date: Fri, 3 Nov 2023 08:06:42 +1100 [thread overview]
Message-ID: <20231103080642.468b331a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
3111add7f414 ("module: Annotate struct module_notes_attrs with __counted_by")
331e833a7606 ("module: Fix comment typo")
dc95e422c283 ("module: Make is_valid_name() return bool")
bac202d3712f ("module: Make is_mapping_symbol() return bool")
b72d5a66766d ("module/decompress: use vmalloc() for gzip decompression workspace")
c7540b27da9e ("MAINTAINERS: add include/linux/module*.h to modules")
130afb8ce111 ("module: Clarify documentation of module_param_call()")
These are commits
ea0b0bcef491 ("module: Annotate struct module_notes_attrs with __counted_by")
fd06da776130 ("module: Fix comment typo")
04311b9b3063 ("module: Make is_valid_name() return bool")
60da3640b07c ("module: Make is_mapping_symbol() return bool")
3737df782c74 ("module/decompress: use vmalloc() for gzip decompression workspace")
62eedac26415 ("MAINTAINERS: add include/linux/module*.h to modules")
2c7ccb3c362b ("module: Clarify documentation of module_param_call()")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-11-02 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 21:06 Stephen Rothwell [this message]
2023-11-02 21:48 ` linux-next: duplicate patches in the modules tree Luis Chamberlain
-- strict thread matches above, loose matches on Subject: below --
2025-01-27 2:59 Stephen Rothwell
2025-01-27 9:02 ` Petr Pavlu
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=20231103080642.468b331a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mcgrof@kernel$(echo .)org \
/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