From: Breno Leitao <leitao@debian.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
leit@meta.com, Michael van der Westhuizen <rmikey@meta.com>,
Andy Shevchenko <andy@kernel.org>,
"open list:I2C SUBSYSTEM HOST DRIVERS"
<linux-i2c@vger.kernel.org>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Do not mark ACPI devices as irq safe
Date: Wed, 14 Aug 2024 01:47:54 -0700 [thread overview]
Message-ID: <ZrxvOr6O8weK5cB6@gmail.com> (raw)
In-Reply-To: <ry4kzh4vr573ymutpjz5sgzmhosn3ekm3jatjy4yfyfm32eqit@cmp376je7viy>
Hello Andi,
On Tue, Aug 13, 2024 at 11:53:17PM +0100, Andi Shyti wrote:
> Hi Breno,
>
> You don't need to resend the patch. Because the changes are only
> in the commit log, I can take care of them.
In fact, the changes are in the code itself, see the changelog:
* Replaced ACPI_HANDLE() by has_acpi_companion() (Andy Shevchenko)
* Expanded the comment before the change (Andy Shevchenko)
> Besides, you also need:
>
> Fixes: ede2299f7101 ("i2c: tegra: Support atomic transfers")
> Cc: <stable@vger.kernel.org> # v5.6+
>
> Can you please check whether this is right?
I would say that we probably want to blame the support for ACPI device,
which came later than ede2299f7101 ("i2c: tegra: Support atomic
transfers").
I'd suggest the following:
Fixes: bd2fdedbf2ba ("i2c: tegra: Add the ACPI support")
CC: <stable@vger.kernel.org> # v5.17+
I am not planning to submit a new patch with these changes, please let
me know if you need action on my side.
Thanks for handling this fix,
--breno
next prev parent reply other threads:[~2024-08-14 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 16:12 [PATCH v2] Do not mark ACPI devices as irq safe Breno Leitao
2024-08-13 19:45 ` Andy Shevchenko
2024-08-13 19:47 ` Wolfram Sang
2024-08-14 12:56 ` Andy Shevchenko
2024-08-13 22:53 ` Andi Shyti
2024-08-14 8:47 ` Breno Leitao [this message]
2024-08-14 11:02 ` Andi Shyti
2024-08-14 13:40 ` Breno Leitao
2024-08-14 22:30 ` Andi Shyti
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=ZrxvOr6O8weK5cB6@gmail.com \
--to=leitao@debian.org \
--cc=andi.shyti@kernel.org \
--cc=andy@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=leit@meta.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rmikey@meta.com \
--cc=thierry.reding@gmail.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