From: Sekhar Nori <nsekhar@ti.com>
To: Michael Turquette <mturquette@baylibre.com>,
David Lechner <david@lechnology.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9] clk: davinci: outstanding fixes
Date: Thu, 31 May 2018 10:13:40 +0530 [thread overview]
Message-ID: <8f188ff5-50d1-f128-ecc5-d25edda325d4@ti.com> (raw)
In-Reply-To: <20180530200947.982.19495@harbor.lan>
On Thursday 31 May 2018 01:39 AM, Michael Turquette wrote:
> Hi David,
>
> Quoting David Lechner (2018-05-25 11:11:41)
>> This is a resend of all of the outstanding DaVinci clock patches plus one new
>> patch. All of the patches (except the new one) have been reviewed and tested
>> by someone other than me.
>>
>> The new patch ("clk: davinci: Fix link errors when not all SoCs are enabled")
>> should be fairly trivial.
>>
>> I am resending them all in one series to hopefully make it easier to get them
>> picked up by having them in the correct order to avoid merge conflicts. This
>> series is based on the clk/clk-davinci-psc-da830 branch.
>
> I picked them all and pushed to clk/clk-davinci based on -rc1. There are
> some comments on the individual patches, all of which are of the "please
> revisit this and fix it up later" variety.
>
> Going forward I'm happy for you and/or Sekhar to send clk PRs to Stephen
> and myself. The same rules apply for PRs: all patches need to be posted
> to the list the old fashioned way for review. But PRs make our lives a
> bit easier, especially when dealing with chip variants from the same SoC
> family like we have with davinci.
Thanks Mike! David is listed as maintainer for drivers/clk/davinci/* and
I believe he can be generating pull requests going forward. I can work
as the backup, of course.
Regards,
Sekhar
prev parent reply other threads:[~2018-05-31 4:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 18:11 David Lechner
2018-05-25 18:11 ` [PATCH 1/9] clk: davinci: pll-dm355: drop pll2_sysclk2 David Lechner
2018-05-25 18:11 ` [PATCH 2/9] clk: davinci: pll-dm355: fix SYSCLKn parent names David Lechner
2018-05-25 18:11 ` [PATCH 3/9] clk: davinci: psc-dm355: fix ASP0/1 clkdev lookups David Lechner
2018-05-25 18:11 ` [PATCH 4/9] clk: davinci: pll-dm646x: keep PLL2 SYSCLK1 always enabled David Lechner
2018-05-30 17:22 ` Michael Turquette
2018-05-30 19:20 ` David Lechner
2018-05-25 18:11 ` [PATCH 5/9] clk: davinci: psc-dm365: fix few clocks David Lechner
2018-05-25 18:11 ` [PATCH 6/9] clk: davinci: pll: allow dev == NULL David Lechner
2018-05-30 19:46 ` Michael Turquette
2018-05-30 19:59 ` David Lechner
2018-05-25 18:11 ` [PATCH 7/9] clk: davinci: da850-pll: change PLL0 to CLK_OF_DECLARE David Lechner
2018-05-25 18:11 ` [PATCH 8/9] clk: davinci: psc: allow for dev == NULL David Lechner
2018-05-25 18:11 ` [PATCH 9/9] clk: davinci: Fix link errors when not all SoCs are enabled David Lechner
2018-05-28 13:43 ` Sekhar Nori
2018-05-28 16:54 ` David Lechner
2018-05-30 20:09 ` [PATCH 0/9] clk: davinci: outstanding fixes Michael Turquette
2018-05-31 4:43 ` Sekhar Nori [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=8f188ff5-50d1-f128-ecc5-d25edda325d4@ti.com \
--to=nsekhar@ti.com \
--cc=david@lechnology.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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 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®