From: Parker Newman <parker@finest.io>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Parker Newman <pnewman@connecttech.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v1 1/1] serial: 8250_exar: Group CTI EEPROM offsets by device
Date: Fri, 20 Sep 2024 11:59:41 -0400 [thread overview]
Message-ID: <20240920115941.1d10f84d@SWDEV2.connecttech.local> (raw)
In-Reply-To: <Zu2ZfpnnY6z4BBG9@smile.fi.intel.com>
On Fri, 20 Sep 2024 18:49:18 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Fri, Sep 20, 2024 at 06:43:24PM +0300, Andy Shevchenko wrote:
> > It's not obvious from the first glance that the list of the CTI EEPROM
> > offsets covers three different models, let's group them accordingly for
> > better readability.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> >
> > Parker, feel free to append this one to your v3 as a last patch.
>
Will do.
> A bit more hints for usage of `b4`. As I described earlier you may use b4
> to gather the tags, but also to inject / append other patches to the series.
>
> Like with this one, after you collected yours, just run
>
> b4 am -s $<message ID of this email thread>
>
> followed by
>
> git am ...
>
> as the tool hints you. It will take care about everything you need.
>
Thanks again for the tips!
-Parker
prev parent reply other threads:[~2024-09-20 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 15:43 [PATCH v1 1/1] serial: 8250_exar: Group CTI EEPROM offsets by device Andy Shevchenko
2024-09-20 15:49 ` Andy Shevchenko
2024-09-20 15:59 ` Parker Newman [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=20240920115941.1d10f84d@SWDEV2.connecttech.local \
--to=parker@finest.io \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pnewman@connecttech.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).