Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Hardik Prakash <hardikprakash.official@gmail.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
	linux-gpio@vger.kernel.org, wsa@kernel.org,
	andriy.shevchenko@intel.com, brgl@bgdev.pl,
	basavaraj.natikar@amd.com, linux-i2c@vger.kernel.org,
	linusw@kernel.org
Subject: Re: [PATCH v6 1/1] i2c: designware: defer probe if child GpioInt controllers are not bound
Date: Fri, 29 May 2026 08:23:45 +0100	[thread overview]
Message-ID: <8444f980-d8d4-4361-acff-8424b4c8cd3f@kernel.org> (raw)
In-Reply-To: <CANTFpSVX8YZxY+6pMcv=HhHBRbkPymox1GHhSCoBHzknatnfQg@mail.gmail.com>

On 5/29/26 07:56, Hardik Prakash wrote:
> On Fri, May 29, 2026, at 04:43, Mario Limonciello wrote:
>> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
>>
>> Please make sure that we drop the now unnecessary patch that was
>> committed from the earlier series when queuing this. If that has
>> already made it into a PR to linus (as part of -fixes or so) we should
>> get it reverted.
> 
> Linus Walleij confirmed it has already been pulled into Torvalds' tree,
> so a revert will be needed. I'll leave that to the maintainers to
> coordinate.
> 
> I'll send v8 now with your Reviewed-by and Bart's Acked-by collected.
> 

IMO - Just send your next version with a revert of that first patch 
frontloaded in the series.

  reply	other threads:[~2026-05-29  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 17:44 [PATCH v6 0/1] i2c: designware: defer probe if child GpioInt controllers are not bound Hardik Prakash
2026-05-23 17:44 ` [PATCH v6 1/1] " Hardik Prakash
2026-05-24  1:47   ` kernel test robot
2026-05-24  5:40     ` Hardik Prakash
2026-05-26 10:42   ` Bartosz Golaszewski
2026-05-28 21:24     ` Mario Limonciello
2026-05-29  6:56       ` Hardik Prakash
2026-05-29  7:23         ` Mario Limonciello [this message]
2026-05-23 17:57 ` [PATCH v6 0/1] " Mario Limonciello
2026-05-26  9:41 ` Bartosz Golaszewski
2026-05-26 10:05   ` Hardik Prakash

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=8444f980-d8d4-4361-acff-8424b4c8cd3f@kernel.org \
    --to=superm1@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=basavaraj.natikar@amd.com \
    --cc=brgl@bgdev.pl \
    --cc=brgl@kernel.org \
    --cc=hardikprakash.official@gmail.com \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.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