From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Laura Nao <laura.nao@collabora.com>,
mika.westerberg@linux.intel.com, linus.walleij@linaro.org,
brgl@bgdev.pl, kernel@collabora.com,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-acpi@vger.kernel.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"kernelci.org bot" <bot@kernelci.org>
Subject: Re: [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs()
Date: Wed, 22 May 2024 08:58:44 +1000 [thread overview]
Message-ID: <20240522085844.16cba3f4@canb.auug.org.au> (raw)
In-Reply-To: <Zkyo6DL7NQltLLNr@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hi Andy,
On Tue, 21 May 2024 17:00:08 +0300 Andy Shevchenko <andriy.shevchenko@linux.intel.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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-05-21 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240513095610.216668-1-laura.nao@collabora.com>
[not found] ` <ZkHlLLLoagsYlll7@smile.fi.intel.com>
2024-05-21 10:01 ` [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs() Linux regression tracking (Thorsten Leemhuis)
2024-05-21 14:00 ` Andy Shevchenko
2024-05-21 14:26 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-21 14:53 ` Andy Shevchenko
2024-05-21 15:14 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-21 15:27 ` Andy Shevchenko
2024-05-21 16:50 ` Andy Shevchenko
2024-05-21 18:41 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-21 22:58 ` Stephen Rothwell [this message]
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=20240522085844.16cba3f4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bot@kernelci.org \
--cc=brgl@bgdev.pl \
--cc=kernel@collabora.com \
--cc=laura.nao@collabora.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=regressions@lists.linux.dev \
/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).