From: Lee Jones <lee@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, Aaro Koskinen <aaro.koskinen@iki.fi>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, Roger Quadros <rogerq@kernel.org>,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: (subset) [PATCH v5 1/3] mfd: twl-core: Add a clock subdevice for the TWL6030
Date: Fri, 25 Oct 2024 09:50:26 +0100 [thread overview]
Message-ID: <20241025085026.GA10824@google.com> (raw)
In-Reply-To: <20241023120432.59cedd0b@akair>
On Wed, 23 Oct 2024, Andreas Kemnade wrote:
> Am Tue, 15 Oct 2024 09:33:10 +0100
> schrieb Lee Jones <lee@kernel.org>:
>
> > On Mon, 14 Oct 2024 18:11:07 +0200, Andreas Kemnade wrote:
> > > Also the TWL6030 has some clocks, so add a subdevice for that.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [1/3] mfd: twl-core: Add a clock subdevice for the TWL6030
> > commit: 5ebc60259a0fdd13aef077726b1773f1ae091efc
> >
> hmm, this does not appear in linux-next. Did anything went wrong?
Looks like a clerical error on my part.
Thanks for noticing. Re-applied and pushed.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-10-25 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 16:11 [PATCH v5 0/3] mfd: twl: Add clock for TWL6030 Andreas Kemnade
2024-10-14 16:11 ` [PATCH v5 1/3] mfd: twl-core: Add a clock subdevice for the TWL6030 Andreas Kemnade
2024-10-15 8:33 ` (subset) " Lee Jones
2024-10-23 10:04 ` Andreas Kemnade
2024-10-25 8:50 ` Lee Jones [this message]
2024-10-14 16:11 ` [PATCH v5 2/3] clk: twl: remove is_prepared Andreas Kemnade
2024-10-17 19:05 ` Stephen Boyd
2024-10-14 16:11 ` [PATCH v5 3/3] clk: twl: add TWL6030 support Andreas Kemnade
2024-10-16 18:51 ` Roger Quadros
2024-10-17 19:05 ` Stephen Boyd
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=20241025085026.GA10824@google.com \
--to=lee@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=khilman@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rogerq@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.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).