From: Luis Chamberlain <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>, pmladek@suse.com
Cc: petr.pavlu@suse.com, prarit@redhat.com, pmladek@suse.com,
mwilck@suse.com, vegard.nossum@oracle.com, ebiederm@xmission.com,
david@redhat.com, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] modules changes for v6.2-rc6
Date: Tue, 24 Jan 2023 13:06:27 -0800 [thread overview]
Message-ID: <Y9BIU5SGOS6YEdSh@bombadil.infradead.org> (raw)
The following changes since commit 7bf70dbb18820b37406fdfa2aaf14c2f5c71a11a:
Merge tag 'vfio-v6.2-rc6' of https://github.com/awilliam/linux-vfio (2023-01-23 11:56:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/ tags/modules-6.2-rc6
for you to fetch changes up to 0254127ab977e70798707a7a2b757c9f3c971210:
module: Don't wait for GOING modules (2023-01-24 12:52:52 -0800)
----------------------------------------------------------------
modules-6.2-rc6
There has been a fix we have been delaying for v6.2 due to lack of
early testing on linux-next. The commit has been sitting on linux-next
since December and testing has also been now a bit extensive by a few
developers. Since this is a fix which definitely will go to v6.3 it
should also apply to v6.2 so if there are any issues we pick them up
earlier rather than later. The fix fixes a regression since v5.3, prior
to me helping with module maintenance, however, the issue is real in
that in the worst case now can prevent boot.
We've discussed all possible corner cases [0] and at last do feel this is
ready for v6.2-rc6.
[0] https://lore.kernel.org/all/Y9A4fiobL6IHp%2F%2FP@bombadil.infradead.org/
----------------------------------------------------------------
Petr Pavlu (1):
module: Don't wait for GOING modules
kernel/module/main.c | 26 +++++++++++++++++++++-----
1 file changed, 21 insertions(+), 5 deletions(-)
next reply other threads:[~2023-01-24 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 21:06 Luis Chamberlain [this message]
2023-01-25 2:23 ` [GIT PULL] modules changes for v6.2-rc6 pr-tracker-bot
2023-08-11 3:48 ` Majordomo not working Leslie Rhorer
2023-08-11 3:53 ` Leslie Rhorer
2023-08-11 4:46 ` Randy Dunlap
2023-08-11 16:51 ` Leslie Rhorer
2023-08-11 16:55 ` Randy Dunlap
2023-08-13 18:32 ` Leslie Rhorer
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=Y9BIU5SGOS6YEdSh@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=prarit@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).