[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yebn8wWvCa4T6ppC@bombadil.infradead.org>
Date: Tue, 18 Jan 2022 08:16:51 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Jessica Yu <jeyu@...nel.org>,
Colin Ian King <colin.king@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Yu Chen <chen.yu@...ystack.cn>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-modules@...r.kernel.org
Subject: Re: Modules updates for v5.17-rc1
On Mon, Jan 17, 2022 at 07:38:25AM +0200, Linus Torvalds wrote:
> On Sat, Jan 15, 2022 at 2:20 AM Luis Chamberlain <mcgrof@...nel.org> wrote:
> >
> > Although this change was only merged on January 11th, the patches have
> > been being reviewed since early december. There was at least one fix
> > already found for it and merged.
>
> Grr..
>
> And that's exactly why it matters not about "being reviewed", but when
> they were in linux-next etc.
>
> I've pulled this, but consider this a complaint. Things should not be
> "reviewed" before the merge window. They should be ready and merged
> and have actually seen some testing.
>
> Review is good. But nothing beats actually being out there and
> actually seeing real-life testing (of course, linux-next probably
> mostly gets build-testing, but what testing it gets is still better
> than not being there).
Understood, that gives me a better ballpark idea of when to defer
things for a next release. Thanks for the feedback.
Luis
Powered by blists - more mailing lists