[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240522085844.16cba3f4@canb.auug.org.au>
Date: Wed, 22 May 2024 08:58:44 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Linux regressions mailing list <regressions@...ts.linux.dev>, Laura Nao
<laura.nao@...labora.com>, mika.westerberg@...ux.intel.com,
linus.walleij@...aro.org, brgl@...ev.pl, kernel@...labora.com,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-acpi@...r.kernel.org, AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>, "kernelci.org bot"
<bot@...nelci.org>
Subject: Re: [PATCH] gpiolib: acpi: Move ACPI device NULL check to
acpi_can_fallback_to_crs()
Hi Andy,
On Tue, 21 May 2024 17:00:08 +0300 Andy Shevchenko <andriy.shevchenko@...uxintel.com> wrote:
>
> Because:
>
> - that's the policy of Linux Next (do not include what's not supposed to be
> merged during merge window), Cc'ed to Stephen to clarify, it might be that
> I'm mistaken
My current daily reports say "Do not add any work intended for v6.11 to
your linux-next included branches until after v6.10-rc1 has been
released". i.e. we don't want new development work added to linux-next
during the merge window as that may just cause unnecessary conflicts or
build failures while we are trying to just get the merge window done.
I have always said (maybe not recently) that bug fixes are always
welcome. Also, more urgent bug fixes often just bypass linux-next.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists