From: Lee Jones <lee@kernel.org>
To: Henning Schild <henning.schild@siemens.com>
Cc: Pavel Machek <pavel@ucw.cz>, Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 0/3] leds: simatic-ipc-leds-gpio: split up
Date: Mon, 15 May 2023 13:12:47 +0100 [thread overview]
Message-ID: <20230515121247.GB10825@google.com> (raw)
In-Reply-To: <20230515120138.66e48bd4@md1za8fc.ad001.siemens.net>
On Mon, 15 May 2023, Henning Schild wrote:
> Am Mon, 15 May 2023 10:50:42 +0100
> schrieb Lee Jones <lee@kernel.org>:
>
> > On Sat, 13 May 2023, Henning Schild wrote:
> >
> > > Ping.
> > >
> > > As far as i remember this one should be ready to merge.
> > >
> > > ACKed by Hans, and Andy had no objections given the maintainers
> > > would accept the patches.
> > >
> > > So i think it is the maintainers turn now, Pavel and/or Lee i
> > > guess.
> >
> > Looks like there are lots of mail threads in reply to each of the
> > patches. If these culminated in acceptance, please collect all of the
> > Acks you've received until this point and submit a [RESEND]. If there
> > are changes to be made still, please do the same but submit as a new
> > version.
>
> Ok i will send it again and include the ACK from Hans. There would be no
> code change. Please review the code already, if you find it acceptable
> we might receive a second ACK from Andy.
Not sure what you mean by 'already'.
I shall not be reviewing this set until it is resent, thanks.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-05-15 12:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 17:02 [PATCH v2 0/3] leds: simatic-ipc-leds-gpio: split up Henning Schild
2023-03-01 17:02 ` [PATCH v2 1/3] leds: simatic-ipc-leds-gpio: move two extra gpio pins into another table Henning Schild
2023-03-01 17:21 ` Andy Shevchenko
2023-03-02 8:33 ` Henning Schild
2023-03-01 17:02 ` [PATCH v2 2/3] leds: simatic-ipc-leds-gpio: split up into multiple drivers Henning Schild
2023-03-01 17:28 ` Andy Shevchenko
2023-03-02 8:40 ` Henning Schild
2023-03-02 15:46 ` Andy Shevchenko
2023-03-02 15:58 ` Henning Schild
2023-03-02 16:21 ` Andy Shevchenko
2023-03-02 17:06 ` Henning Schild
2023-05-15 11:14 ` Henning Schild
2023-03-01 17:02 ` [PATCH v2 3/3] leds: simatic-ipc-leds-gpio: introduce more Kconfig switches Henning Schild
2023-03-01 17:29 ` Andy Shevchenko
2023-03-02 8:31 ` Henning Schild
2023-03-01 18:04 ` Hans de Goede
2023-03-02 8:47 ` Henning Schild
2023-03-02 9:02 ` Hans de Goede
2023-03-02 10:14 ` Henning Schild
2023-05-15 10:41 ` Henning Schild
2023-05-15 11:24 ` Hans de Goede
2023-03-01 17:30 ` [PATCH v2 0/3] leds: simatic-ipc-leds-gpio: split up Andy Shevchenko
2023-03-02 10:19 ` Henning Schild
2023-05-13 10:08 ` Henning Schild
2023-05-15 9:50 ` Lee Jones
2023-05-15 10:01 ` Henning Schild
2023-05-15 12:12 ` Lee Jones [this message]
2023-05-15 15:06 ` Henning Schild
2023-05-15 15:40 ` Lee Jones
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=20230515121247.GB10825@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=henning.schild@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.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