From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>,
Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH net-next] i2c: tegra: runtime PM is not IRQ-safe
Date: Tue, 17 Feb 2026 16:04:15 +0000 [thread overview]
Message-ID: <aZSRfzXNnzzc9MiL@shell.armlinux.org.uk> (raw)
In-Reply-To: <a97f726e-58f0-4cdc-8e4c-a11c1e1c76ef@nvidia.com>
On Tue, Feb 17, 2026 at 03:55:47PM +0000, Jon Hunter wrote:
> Hi Russell,
>
> Mikko recently posted this fix [0]. Hopefully, this also works?
>
> Thanks
> Jon
>
> [0] https://lore.kernel.org/linux-tegra/20260217-i2c-dpaux-irqsafe-v2-1-635a4c43b1a7@nvidia.com/T/#u
Looks like it probably would do, but I note that it fixes two problems.
What happened to "fix one problem with one patch" ?
From Documentation/process/submitting-patches.rst:
Solve only one problem per patch. If your description starts to get
long, that's a sign that you probably need to split up your patch.
See :ref:`split_changes`.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-02-17 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 15:40 [PATCH net-next] i2c: tegra: runtime PM is not IRQ-safe Russell King (Oracle)
2026-02-17 15:50 ` Russell King (Oracle)
2026-02-17 15:55 ` Jon Hunter
2026-02-17 16:04 ` Russell King (Oracle) [this message]
2026-02-17 16:15 ` Jon Hunter
2026-02-17 16:40 ` Russell King (Oracle)
2026-02-17 16:46 ` Jon Hunter
2026-02-18 1:35 ` Mikko Perttunen
2026-02-18 8:30 ` Jon Hunter
2026-03-18 18:17 ` Russell King (Oracle)
2026-03-19 2:16 ` Mikko Perttunen
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=aZSRfzXNnzzc9MiL@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.