From: Petr Pavlu <petr.pavlu@suse•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Luis Chamberlain <mcgrof@kernel•org>,
Sami Tolvanen <samitolvanen@google•com>,
Daniel Gomez <da.gomez@samsung•com>,
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: Mon, 27 Jan 2025 10:02:23 +0100 [thread overview]
Message-ID: <8fcc8318-2d90-485d-acdd-196bda95cd6a@suse.com> (raw)
In-Reply-To: <20250127135935.0195bc68@canb.auug.org.au>
On 1/27/25 03:59, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 0217859ce172 ("module: sign with sha512 instead of sha1 by default")
> 0dea980a17a3 ("module: sysfs: Drop member 'module_sect_attrs::nsections'")
> 0e436d14d0b9 ("module: Put known GPL offenders in an array")
> 25aa76116052 ("module: Constify 'struct module_attribute'")
> 570f7776db9c ("module: Split module_enable_rodata_ro()")
> 75b519abc918 ("module: sysfs: Simplify section attribute allocation")
> 8c82fb5240f7 ("module: Extend the preempt disabled section in dereference_symbol_descriptor().")
> 993026197341 ("params: Prepare for 'const struct module_attribute *'")
> 9b894ee43337 ("module: Don't fail module loading when setting ro_after_init section RO failed")
> c027a83a0375 ("module: sysfs: Drop member 'module_sect_attr::address'")
> cb80af8451df ("module: Handle 'struct module_version_attribute' as const")
> cd8026d4bda8 ("module: sysfs: Drop 'struct module_sect_attr'")
> e6ea40687ff0 ("module: sysfs: Use const 'struct bin_attribute'")
> fc15d675bc49 ("module: sysfs: Add notes attributes through attribute_group")
>
> Presumably rebased before asking Linus to merge them :-(
Right, I rebased modules-next locally, pushed a tag for a pull request
which has been merged, but I forgot to push the actual branch. Sorry
about that, it should be fixed now.
I could have arguably saved myself time and trouble by not rebasing
modules-next in this case, which might have been also better from
a testing perspective.
--
Thanks,
Petr
next prev parent reply other threads:[~2025-01-27 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 2:59 linux-next: duplicate patches in the modules tree Stephen Rothwell
2025-01-27 9:02 ` Petr Pavlu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 21:06 Stephen Rothwell
2023-11-02 21:48 ` Luis Chamberlain
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=8fcc8318-2d90-485d-acdd-196bda95cd6a@suse.com \
--to=petr.pavlu@suse$(echo .)com \
--cc=da.gomez@samsung$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mcgrof@kernel$(echo .)org \
--cc=samitolvanen@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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