From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
Hardik Prakash <hardikprakash.official@gmail.com>,
linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
wsa@kernel.org, mario.limonciello@amd.com, brgl@bgdev.pl,
basavaraj.natikar@amd.com, linusw@kernel.org, nathan@kernel.org,
chaitanya.kumar.borah@intel.com
Subject: Re: [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound"
Date: Mon, 15 Jun 2026 13:11:29 +0200 [thread overview]
Message-ID: <ai_d4eIId8Ml9g7I@ninjato> (raw)
In-Reply-To: <ai_cAd41W3iX1ic-@zenone.zhora.eu>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
> > $ git tag --contains ef76a3a28c79b6288
> > next-20260601
> > next-20260602
> > next-20260603
> > next-20260604
> > next-20260605
> > next-20260608
> > next-20260609
> > next-20260610
> > next-20260611
>
> Yes, but I'm not finding out how it got there. I only see it in
> one of Wolfram's branches, but I don't think it came in that way.
IIRC I asked Linus Walleij to handle this via the GPIO tree because the
proper fix landed there and the I2C addition was a mere cleanup from a
previous attempt to fix the issue.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-15 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:37 [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" Hardik Prakash
2026-06-10 10:47 ` Andy Shevchenko
2026-06-10 11:27 ` Borah, Chaitanya Kumar
2026-06-10 16:59 ` Nathan Chancellor
2026-06-14 21:56 ` Andi Shyti
2026-06-15 10:11 ` Andy Shevchenko
2026-06-15 11:07 ` Andi Shyti
2026-06-15 11:11 ` Wolfram Sang [this message]
2026-06-15 12:23 ` Linus Walleij
2026-06-15 12:21 ` Linus Walleij
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=ai_d4eIId8Ml9g7I@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=basavaraj.natikar@amd.com \
--cc=brgl@bgdev.pl \
--cc=chaitanya.kumar.borah@intel.com \
--cc=hardikprakash.official@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nathan@kernel.org \
--cc=wsa@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.