From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Hardik Prakash <hardikprakash.official@gmail.com>
Cc: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
wsa@kernel.org, andriy.shevchenko@intel.com,
mario.limonciello@amd.com, brgl@bgdev.pl,
basavaraj.natikar@amd.com, linusw@kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
"Mario Limonciello (AMD)" <superm1@kernel.org>,
kernel test robot <lkp@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
ravitejax.veesam@intel.com
Subject: Re: [PATCH v8 2/2] i2c: designware: defer probe if child GpioInt controllers are not bound
Date: Tue, 9 Jun 2026 14:37:43 +0200 [thread overview]
Message-ID: <aigJF6hd1EjRiGc-@ninjato> (raw)
In-Reply-To: <CANTFpSV7N=5U9yuXcU-D=PDpwj=kD__JU89UGL1HQOYiaL77qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
> Linus, could you please drop commit ef76a3a28c79 from your fixes tree?
> The regression affects multiple machines including Intel CI and Nathan
> Chancellor's test systems.
>
> I will send a corrected version once the rewrite is complete.
Sending a revert patch seems like the better choice to me. His fixes
branch is probably in -next already?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-06-09 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260529100838.8896-1-hardikprakash.official@gmail.com>
[not found] ` <20260529100838.8896-3-hardikprakash.official@gmail.com>
[not found] ` <90656be5-eca0-4a09-9b19-0c6e85f1d455@intel.com>
2026-06-09 11:54 ` [PATCH v8 2/2] i2c: designware: defer probe if child GpioInt controllers are not bound Hardik Prakash
2026-06-09 12:37 ` 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=aigJF6hd1EjRiGc-@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andriy.shevchenko@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=basavaraj.natikar@amd.com \
--cc=brgl@bgdev.pl \
--cc=chaitanya.kumar.borah@intel.com \
--cc=hardikprakash.official@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mario.limonciello@amd.com \
--cc=ravitejax.veesam@intel.com \
--cc=superm1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox