public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Laura Nao <laura.nao@collabora.com>
Cc: 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: Mon, 13 May 2024 13:02:20 +0300	[thread overview]
Message-ID: <ZkHlLLLoagsYlll7@smile.fi.intel.com> (raw)
In-Reply-To: <20240513095610.216668-1-laura.nao@collabora.com>

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.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-05-13 10:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  9:56 [PATCH] gpiolib: acpi: Move ACPI device NULL check to acpi_can_fallback_to_crs() Laura Nao
2024-05-13 10:02 ` Andy Shevchenko [this message]
2024-05-21 10:01   ` 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

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=ZkHlLLLoagsYlll7@smile.fi.intel.com \
    --to=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 \
    /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