From: Luis Chamberlain <mcgrof@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the modules tree
Date: Thu, 2 Nov 2023 14:48:08 -0700 [thread overview]
Message-ID: <ZUQZGLDYL1/eoyzj@bombadil.infradead.org> (raw)
In-Reply-To: <20231103080642.468b331a@canb.auug.org.au>
On Fri, Nov 03, 2023 at 08:06:42AM +1100, Stephen Rothwell wrote:
> 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.
Fixed.
Luis
next prev parent reply other threads:[~2023-11-02 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 21:06 linux-next: duplicate patches in the modules tree Stephen Rothwell
2023-11-02 21:48 ` Luis Chamberlain [this message]
-- 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=ZUQZGLDYL1/eoyzj@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).