From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Myeonghun Pak <mhun512@gmail.com>
Cc: andi.shyti@kernel.org, linux-renesas-soc@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
ae878000@gmail.com
Subject: Re: [PATCH] i2c: sh_mobile: request IRQs after mapping registers
Date: Wed, 4 Nov 2026 15:21:47 +0200 [thread overview]
Message-ID: <ausxa9vGb2laTzbE@shikoro> (raw)
In-Reply-To: <ausul_FO8-1JKEmL@shikoro>
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
> won't matter here, as I see it. Unless the later pm_runtime_get_sync()
> the device should not(tm) be able to send irqs. Famous last words...
Which only matters during probe(), not during teardown... sorry for the
noise! Patch is still good.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-11-04 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 3:35 [PATCH] i2c: sh_mobile: request IRQs after mapping registers Myeonghun Pak
2026-10-23 22:09 ` Andi Shyti
2026-10-26 8:41 ` Geert Uytterhoeven
2026-11-04 13:09 ` Wolfram Sang
2026-11-04 13:21 ` Wolfram Sang [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=ausxa9vGb2laTzbE@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=ae878000@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mhun512@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