From: Kris Bahnsen <kris@embeddedTS.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Featherston <mark@embeddedts.com>
Subject: Re: [PATCH v3 1/2] gpio: ts4900: Do not set DAT and OE together
Date: Thu, 10 Mar 2022 11:47:20 -0800 [thread overview]
Message-ID: <1646941640.2804.4.camel@embeddedTS.com> (raw)
In-Reply-To: <CAMRc=MerqLPZSCd8+YSAwJPe1_zpOYQK5C-DXirC6dvR4Yss5g@mail.gmail.com>
On Thu, 2022-03-10 at 20:30 +0100, Bartosz Golaszewski wrote:
> On Thu, Mar 10, 2022 at 6:36 PM Kris Bahnsen <kris@embeddedts.com> wrote:
> >
> > On Thu, 2022-03-10 at 16:48 +0200, Andy Shevchenko wrote:
> > > On Thu, Mar 10, 2022 at 2:22 PM Kris Bahnsen <kris@embeddedts.com> wrote:
> > > >
> > > > From: Mark Featherston <mark@embeddedTS.com>
> > >
> > > Same comments as per v2.
> > >
> >
> > Thanks, I'll get a v4 put together shortly to clean that up.
>
> Hey Kris,
>
> I already sent it out to Linus, please create a follow-up patch for that.
>
> Bart
Can you please clarify what that entails since Andy had requested changes to the
commit message. Should I just create a new patch on top of the commit already on
master to address the comment changes? How would I address commit message changes,
or is that not my responsibility at this point?
Thanks for all the help on learning this process thus far!
Kris
next prev parent reply other threads:[~2022-03-10 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 1:16 [PATCH v3 0/2] gpio: ts4900: Do not set DAT and OE together Kris Bahnsen
2022-03-10 1:16 ` [PATCH v3 1/2] " Kris Bahnsen
2022-03-10 9:06 ` Bartosz Golaszewski
2022-03-10 14:48 ` Andy Shevchenko
2022-03-10 17:36 ` Kris Bahnsen
2022-03-10 19:30 ` Bartosz Golaszewski
2022-03-10 19:47 ` Kris Bahnsen [this message]
2022-03-11 11:25 ` Andy Shevchenko
2022-03-10 1:16 ` [PATCH v3 2/2] gpio: ts4900: Use SPDX header Kris Bahnsen
2022-03-10 9:06 ` 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=1646941640.2804.4.camel@embeddedTS.com \
--to=kris@embeddedts.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@embeddedts.com \
/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).