From: Luis Chamberlain <mcgrof@kernel.org>
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: david@redhat.com, Petr Mladek <pmladek@suse.com>,
prarit@redhat.com, mwilck@suse.com,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] module: Don't wait for GOING modules
Date: Mon, 12 Dec 2022 18:58:35 -0800 [thread overview]
Message-ID: <Y5fqW7hQy+WbTh3R@bombadil.infradead.org> (raw)
In-Reply-To: <0017c9ce-7e92-6010-7bc9-716131a25ec5@suse.com>
On Mon, Dec 12, 2022 at 12:29:02PM +0100, Petr Pavlu wrote:
> On 12/8/22 03:44, Luis Chamberlain wrote:
> > On Wed, Dec 07, 2022 at 04:15:21PM +0100, Petr Mladek wrote:
> >> Reviewed-by: Petr Mladek <pmladek@suse.com>
> >
> > Queued onto modules-next.
>
> Thanks both.
I'm **terribly sorry** for dropping this to Linus' pull request late
but I kept trying to justify a few things and I couldn't do it, and
so I'll reply to this patch with my last minute observations soon.
I figured it was better to be safe than sorry and the potential for
yet *more* regressions was *real* and I really wanted to avoid us
having to crunch / race for a fix over the holidays.
I will leave the fix as-is now in modules-next though, so it can get
more testing, but indeed, I don't feel quite ready for the masses
specially before the holidays.
Luis
next prev parent reply other threads:[~2022-12-13 2:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 10:35 [PATCH v2] module: Don't wait for GOING modules Petr Pavlu
2022-12-05 19:54 ` Petr Mladek
2022-12-06 16:57 ` Petr Pavlu
2022-12-07 15:15 ` Petr Mladek
2022-12-08 2:44 ` Luis Chamberlain
2022-12-12 11:29 ` Petr Pavlu
2022-12-13 2:58 ` Luis Chamberlain [this message]
2022-12-13 5:09 ` Luis Chamberlain
2022-12-13 10:17 ` Petr Mladek
2022-12-13 13:36 ` Petr Pavlu
2023-01-18 0:04 ` Luis Chamberlain
2023-01-18 0:18 ` Luis Chamberlain
2023-01-18 15:12 ` Petr Pavlu
2023-01-18 18:42 ` Luis Chamberlain
2023-01-19 12:26 ` Petr Pavlu
2023-01-19 15:47 ` Petr Mladek
2023-01-20 0:51 ` Luis Chamberlain
2023-01-20 0:58 ` Luis Chamberlain
2023-01-21 22:40 ` Luis Chamberlain
2023-03-11 21:36 ` Luis Chamberlain
2023-03-12 6:25 ` Lucas De Marchi
2023-03-22 22:31 ` Luis Chamberlain
2023-03-23 15:01 ` Lucas De Marchi
2023-03-23 15:08 ` Luis Chamberlain
2023-03-24 6:03 ` Lucas De Marchi
2023-03-24 18:47 ` Luis Chamberlain
2023-01-24 19:58 ` Luis Chamberlain
2023-01-18 20:02 ` Borislav Petkov
2023-01-19 1:23 ` Luis Chamberlain
2023-01-19 23:37 ` Luis Chamberlain
2023-01-19 1:15 ` Lucas De Marchi
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=Y5fqW7hQy+WbTh3R@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=david@redhat.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=stable@vger.kernel.org \
/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).