From: Arnd Bergmann <arnd@arndb.de>
To: Roman Volkov <v1ron@mail.ru>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>,
Roman Volkov <rvolkov@v1ros.org>,
Tony Prisk <linux@prisktech.co.nz>
Subject: Re: [PATCH 2/2] clk/vt8500: Fix compilation warnings
Date: Tue, 31 May 2016 22:15:38 +0200 [thread overview]
Message-ID: <30846983.uaNfNPJlta@wuerfel> (raw)
In-Reply-To: <20160531213854.343e6129@v1ron-s7>
On Tuesday, May 31, 2016 9:38:54 PM CEST Roman Volkov wrote:
>
> Arnd, your version is fine for me. We may apply it instead.
>
> As you can see, I attached another patch where the logic for WM8650 is
> completely reworked. This patch also removes the warning, that is why
> fixing the wm8650 function is not necessary.
>
> What about the WM8650 enhancement? Can I apply it on top of your
> changes?
I think the easiest way is if you pick up my patch and submit it together
with your other patch as a series (keeping my From: line and adding your
Signed-off-by: below mine).
My patch should probably go first so we can get it into linux-4.7, while
I assume your other one is for 4.8? If we want both in 4.7, either order
is fine.
Arnd
next prev parent reply other threads:[~2016-05-31 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 20:07 [PATCH 0/2] Rework clk/vt8500 wm8650_find_pll_bits() Roman Volkov
2016-05-24 20:07 ` [PATCH 1/2] clk/vt8500: Rework wm8650_find_pll_bits() Roman Volkov
2016-05-24 20:07 ` [PATCH 2/2] clk/vt8500: Fix compilation warnings Roman Volkov
2016-05-31 10:51 ` Arnd Bergmann
2016-05-31 18:38 ` Roman Volkov
2016-05-31 20:15 ` Arnd Bergmann [this message]
2016-06-01 22:07 ` Stephen Boyd
2016-05-31 6:23 ` [PATCH 0/2] Rework clk/vt8500 wm8650_find_pll_bits() Roman Volkov
2016-06-01 22:06 ` 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=30846983.uaNfNPJlta@wuerfel \
--to=arnd@arndb.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=mturquette@baylibre.com \
--cc=rvolkov@v1ros.org \
--cc=sboyd@codeaurora.org \
--cc=v1ron@mail.ru \
/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