From: Lars Povlsen <lars.povlsen@microchip.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Lars Povlsen <lars.povlsen@microchip.com>,
SoC Team <soc@kernel.org>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
linux-clk <linux-clk@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH linux-next] clk: sparx5: Review changes
Date: Tue, 28 Jul 2020 09:53:04 +0200 [thread overview]
Message-ID: <87tuxsf53z.fsf@soft-dev15.microsemi.net> (raw)
In-Reply-To: <159588781925.1360974.3928941757935200801@swboyd.mtv.corp.google.com>
Stephen Boyd writes:
> Quoting Arnd Bergmann (2020-07-27 13:11:49)
>> On Mon, Jul 27, 2020 at 9:39 PM Stephen Boyd <sboyd@kernel.org> wrote:
>> >
>> > Why was the clk driver merged to linux-next outside of the clk tree? Was
>> > there some sort of dependency?
>>
>> I merged the entire series of the base platform support along with
>> a few core drivers. I had asked for the series to be submitted to
>> soc@kernel.org after all parts had been reviewed, but I missed that
>> the clk driver was still missing maintainer review (I saw you had
>> reviewed some patches, but apparently that was just the binding,
>> not the driver).
>>
>> I rebased the 'arm/newsoc' branch the other day to fix another mistake,
>> so if you prefer, I can rebase it again and drop the clk driver or
>> all the sparx5 patches.
>>
>
> Yes, please just drop the clk driver and I can pick it up for the next
> merge window from the list and all the fixes can be rolled into one
> patch.
Sorry for all the commotion!
With Stephen's comments I assume I don't have to submit anything new,
at least not right now.
Otherwise, please let me know.
Cheers,
--
Lars Povlsen,
Microchip
WARNING: multiple messages have this Message-ID (diff)
From: Lars Povlsen <lars.povlsen@microchip.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Arnd Bergmann <arnd@arndb.de>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
linux-kernel@vger.kernel.org,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
SoC Team <soc@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-clk <linux-clk@vger.kernel.org>,
Lars Povlsen <lars.povlsen@microchip.com>
Subject: Re: [PATCH linux-next] clk: sparx5: Review changes
Date: Tue, 28 Jul 2020 09:53:04 +0200 [thread overview]
Message-ID: <87tuxsf53z.fsf@soft-dev15.microsemi.net> (raw)
In-Reply-To: <159588781925.1360974.3928941757935200801@swboyd.mtv.corp.google.com>
Stephen Boyd writes:
> Quoting Arnd Bergmann (2020-07-27 13:11:49)
>> On Mon, Jul 27, 2020 at 9:39 PM Stephen Boyd <sboyd@kernel.org> wrote:
>> >
>> > Why was the clk driver merged to linux-next outside of the clk tree? Was
>> > there some sort of dependency?
>>
>> I merged the entire series of the base platform support along with
>> a few core drivers. I had asked for the series to be submitted to
>> soc@kernel.org after all parts had been reviewed, but I missed that
>> the clk driver was still missing maintainer review (I saw you had
>> reviewed some patches, but apparently that was just the binding,
>> not the driver).
>>
>> I rebased the 'arm/newsoc' branch the other day to fix another mistake,
>> so if you prefer, I can rebase it again and drop the clk driver or
>> all the sparx5 patches.
>>
>
> Yes, please just drop the clk driver and I can pick it up for the next
> merge window from the list and all the fixes can be rolled into one
> patch.
Sorry for all the commotion!
With Stephen's comments I assume I don't have to submit anything new,
at least not right now.
Otherwise, please let me know.
Cheers,
--
Lars Povlsen,
Microchip
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-28 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 11:22 [PATCH linux-next] clk: sparx5: Review changes Lars Povlsen
2020-07-27 11:22 ` Lars Povlsen
2020-07-27 12:02 ` Arnd Bergmann
2020-07-27 12:02 ` Arnd Bergmann
[not found] ` <159587873833.1360974.11729154337431621644@swboyd.mtv.corp.google.com>
2020-07-27 20:11 ` Arnd Bergmann
2020-07-27 20:11 ` Arnd Bergmann
[not found] ` <159588781925.1360974.3928941757935200801@swboyd.mtv.corp.google.com>
2020-07-28 7:53 ` Lars Povlsen [this message]
2020-07-28 7:53 ` Lars Povlsen
2020-07-28 8:31 ` Stephen Boyd
2020-07-28 9:23 ` Arnd Bergmann
2020-07-28 9:23 ` Arnd Bergmann
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=87tuxsf53z.fsf@soft-dev15.microsemi.net \
--to=lars.povlsen@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.