From: "Esteban Blanc" <eblanc@baylibre.com>
To: "Andy Shevchenko" <andy.shevchenko@gmail.com>
Cc: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<linux-kernel@vger.kernel.org>, <linux-rtc@vger.kernel.org>,
<jpanis@baylibre.com>, <jneanne@baylibre.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH v8] rtc: tps6594: Add driver for TPS6594 RTC
Date: Fri, 03 Nov 2023 09:55:15 +0100 [thread overview]
Message-ID: <CWP1UD343WSC.32F81J6ROV2YO@burritosblues> (raw)
In-Reply-To: <CAHp75VdV5A+WpWj2eY9o_2wwPB7GTi6Eig7YyV8urdv1P3utgQ@mail.gmail.com>
On Thu Nov 2, 2023 at 5:46 PM CET, Andy Shevchenko wrote:
> On Thu, Nov 2, 2023 at 6:17 PM Esteban Blanc <eblanc@baylibre.com> wrote:
> > On Thu Nov 2, 2023 at 5:00 PM CET, Andy Shevchenko wrote:
> > > On Thu, Nov 2, 2023 at 3:26 PM Esteban Blanc <eblanc@baylibre.com> wrote:
> > >
> > > > Notes:
> > > > This patch was picked from a series since there is no dependency between
> > > > the two patches.
> > >
> > > Not sure if RTC maintainer uses the b4 tool, but as I said in previous
> > > email for pinctrl change, there is no need to resend. b4 has an
> > > ability to select patches from the series to be applied.
> >
> > Oh that's good to know, I was not aware of that.
> > I resent it because there was some minor nits that I fixed on both
> > patches.
>
> Ah, that was not reflected in the changelog...
Just after the line you quoted, there is "Changes since v7". Maybe I
should have put it near the other ones. Sorry about that.
Best regards,
--
Esteban Blanc
BayLibre
next prev parent reply other threads:[~2023-11-03 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 13:26 Esteban Blanc
2023-11-02 16:00 ` Andy Shevchenko
2023-11-02 16:17 ` Esteban Blanc
2023-11-02 16:46 ` Andy Shevchenko
2023-11-02 16:50 ` Alexandre Belloni
2023-11-02 17:00 ` Andy Shevchenko
2023-11-02 17:04 ` Alexandre Belloni
2023-11-03 8:55 ` Esteban Blanc [this message]
2023-11-03 14:10 ` Andy Shevchenko
2023-11-03 6:52 ` Krzysztof Kozlowski
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=CWP1UD343WSC.32F81J6ROV2YO@burritosblues \
--to=eblanc@baylibre.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=andy.shevchenko@gmail.com \
--cc=jneanne@baylibre.com \
--cc=jpanis@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=u-kumar1@ti.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
all inboxes | Powered by JetHome®