From: David Lechner <david@lechnology.com>
To: Sekhar Nori <nsekhar@ti.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Kevin Hilman <khilman@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Ohad Ben-Cohen <ohad@wizery.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
linux-remoteproc@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v7 0/4] ARM: davinci: complete the conversion to using the reset framework
Date: Mon, 2 Jul 2018 10:27:53 -0500 [thread overview]
Message-ID: <345aed22-629a-abf6-df22-adee88a43df6@lechnology.com> (raw)
In-Reply-To: <e4bd9f57-617a-a59e-5d05-be1a6b3e6b3d@ti.com>
On 07/02/2018 07:08 AM, Sekhar Nori wrote:
> Hi Bjorn,
>
> On Thursday 21 June 2018 05:11 PM, Bartosz Golaszewski wrote:
>> 2018-06-21 12:52 GMT+02:00 Sekhar Nori <nsekhar@ti.com>:
>>> Hi Bartosz,
>>>
>>> On Thursday 21 June 2018 01:07 PM, Bartosz Golaszewski wrote:
>>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>>
>>>> These are the remaining patches that still need to be merged in order
>>>> to complete the conversion of the davinci dsp driver to using the reset
>>>> framework.
>>>>
>>>> They apply on top of v4.18-rc1 with David Lechner's remaining patches
>>>> merged.
>>>
>>> Series looks good to me.
>>>
>>> To preserve bisect, shouldn't the order of applying be patch #3, #4, #1
>>> and #2 ?
>>>
>>> Given the dependencies and to preserve bisect its easiest if I take the
>>> series with acks from remoteproc and clock maintainers.
>>>
>>> Open to other suggestions as well.
>>>
>>> Thanks,
>>> Sekhar
>>
>> Oops you're right about the order. Do you want me to resend?
>
> With your ack, I can queue 1/4 for v4.19 and provide an immutable commit
> to you (on top of v4.18-rc1) for you to merge any further changes you
> want to queue from your tree.
>
> Bartosz, given the number of moving pieces, I think its better to keep
> 2/4 for v4.20 release - once all other other dependencies have been merged.
I was thinking the same thing as well. I will pick it up in a
clk-davinci-4.20 branch if that sounds OK.
next prev parent reply other threads:[~2018-07-02 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 7:37 [PATCH v7 0/4] ARM: davinci: complete the conversion to using the reset framework Bartosz Golaszewski
2018-06-21 7:37 ` [PATCH v7 1/4] remoteproc/davinci: use " Bartosz Golaszewski
2018-07-23 8:03 ` Bartosz Golaszewski
2018-07-31 4:25 ` Bjorn Andersson
2018-07-31 7:55 ` Bartosz Golaszewski
2018-07-31 10:04 ` Sekhar Nori
2018-06-21 7:37 ` [PATCH v7 2/4] clk: davinci: kill davinci_clk_reset_assert/deassert() Bartosz Golaszewski
2018-07-06 17:54 ` David Lechner
2018-10-02 15:08 ` Bartosz Golaszewski
2018-10-02 15:28 ` David Lechner
2018-10-02 15:54 ` Stephen Boyd
2018-06-21 7:37 ` [PATCH v7 3/4] ARM: davinci: dts: make psc0 a reset provider Bartosz Golaszewski
2018-07-02 11:57 ` Sekhar Nori
2018-06-21 7:37 ` [PATCH v7 4/4] ARM: davinci: dts: add a reset control to the dsp node Bartosz Golaszewski
2018-07-02 12:02 ` Sekhar Nori
2018-06-21 10:52 ` [PATCH v7 0/4] ARM: davinci: complete the conversion to using the reset framework Sekhar Nori
2018-06-21 11:41 ` Bartosz Golaszewski
2018-07-02 12:08 ` Sekhar Nori
2018-07-02 15:27 ` David Lechner [this message]
2018-07-03 4:42 ` Sekhar Nori
2018-07-31 4:34 ` Bjorn Andersson
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=345aed22-629a-abf6-df22-adee88a43df6@lechnology.com \
--to=david@lechnology.com \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=nsekhar@ti.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).