Received-SPF: pass (google.com: domain of linux-kernel+bounces-185046-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Date: Tue, 21 May 2024 17:00:08 +0300
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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()
Message-ID: <Zkyo6DL7NQltLLNr@smile.fi.intel.com>
References: <20240513095610.216668-1-laura.nao@collabora.com>
 <ZkHlLLLoagsYlll7@smile.fi.intel.com>
 <b20b567f-ce96-45e8-aab7-29768f8313f5@leemhuis.info>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b20b567f-ce96-45e8-aab7-29768f8313f5@leemhuis.info>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo

On Tue, May 21, 2024 at 12:01:17PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 13.05.24 12:02, Andy Shevchenko wrote:
> > On Mon, May 13, 2024 at 11:56:10AM +0200, Laura Nao wrote:
> >> Following the relocation of the function call outside of
> >> __acpi_find_gpio(), move the ACPI device NULL check to
> >> acpi_can_fallback_to_crs().
> > 
> > Thank you, I'll add this to my tree as we have already the release happened.
> > I will be available after v6.10-rc1 is out.
> 
> Hmm, what exactly do you mean with that? It sounds as you only want to
> add this to the tree once -rc1 is out -- which seems likely at this
> point, as that patch is not yet in -next. If that's the case allow me to
> ask: why?

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

- the process of how we maintain the branches is to have them based on top of
  rc1 (rarely on other rcX and never on an arbitrary commit from vanilla

> I'd say it should be fixes rather sooner than later, as other
> people might run into this as well and then have to deal with bisecing,
> reporting, ...

Yes, but we have a process during merge window, it's special and different
from vX.Y-rc1..vX.Y times.

-- 
With Best Regards,
Andy Shevchenko