From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Hans de Goede <hansg@kernel.org>
Cc: Richard Hughes <rhughes@redhat.com>,
linux-i2c@vger.kernel.org, linux-usb@vger.kernel.org,
linux-gpio@vger.kernel.org,
Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Wolfram Sang <wsa@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 2/3] gpio: Add Intel USBIO GPIO driver
Date: Wed, 10 Sep 2025 15:18:06 +0200 [thread overview]
Message-ID: <CAMRc=MeHefqC-8qY3SZNhXSjyu9VnMnx-N5bWeBxVh0TpwAUOA@mail.gmail.com> (raw)
In-Reply-To: <a77d0593-4001-4315-b8de-22c4b85f213f@kernel.org>
On Wed, Sep 10, 2025 at 1:34 PM Hans de Goede <hansg@kernel.org> wrote:
>
> Thank you I'll go and preparare a standalone v3
> (since the other 2 patches have no reviews yet).
>
Please, don't do this. This is a great way to confuse everyone involved. :(
> As mentioned in the cover-letter it is probably easiest
> if Greg merges the entire series through his usb tree
> once everything has been reviewed.
>
> Once I've send it, can you please ack v3 for merging through
> Greg's USB tree?
>
I would prefer to ack a patch that's part of a proper series, this
split makes no sense.
Bart
next prev parent reply other threads:[~2025-09-10 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 17:50 [PATCH v2 0/3] usb/gpio/i2c: Add Intel USBIO USB IO-expander drivers Hans de Goede
2025-09-07 17:50 ` [PATCH v2 1/3] usb: misc: Add Intel USBIO bridge driver Hans de Goede
2025-09-07 17:50 ` [PATCH v2 2/3] gpio: Add Intel USBIO GPIO driver Hans de Goede
2025-09-09 9:58 ` Bartosz Golaszewski
2025-09-10 11:34 ` Hans de Goede
2025-09-10 13:18 ` Bartosz Golaszewski [this message]
2025-09-10 13:23 ` Hans de Goede
2025-09-07 17:50 ` [PATCH v2 3/3] i2c: Add Intel USBIO I2C driver Hans de Goede
2025-09-10 13:25 ` [PATCH v2 0/3] usb/gpio/i2c: Add Intel USBIO USB IO-expander drivers Greg Kroah-Hartman
2025-09-10 13:36 ` Hans de Goede
2025-09-10 13:47 ` Bartosz Golaszewski
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='CAMRc=MeHefqC-8qY3SZNhXSjyu9VnMnx-N5bWeBxVh0TpwAUOA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andi.shyti@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=israel.a.cepeda.lopez@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rhughes@redhat.com \
--cc=sakari.ailus@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).