From: "Andreas Färber" <afaerber@suse.de>
To: Carlo Caione <carlo@caione.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Matthias Brugger <mbrugger@suse.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk <linux-clk@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-meson@googlegroups.com
Subject: Re: [PATCH] clk: meson: Fix meson_clk_register_clks() signature type mismatch
Date: Mon, 8 Feb 2016 11:55:44 +0100 [thread overview]
Message-ID: <56B87430.3040804@suse.de> (raw)
In-Reply-To: <CAOQ7t2YwHa7cJdqv4m8rPx50ZnFZJJzcU2AjtE=Q2AYEAf84hg@mail.gmail.com>
Am 08.02.2016 um 09:34 schrieb Carlo Caione:
> On Sun, Feb 7, 2016 at 10:13 PM, Andreas Färber <afaerber@suse.de> wrote:
>> As preparation for arm64 based mesongxbb, which pulls in this code once
>> enabling ARCH_MESON, fix a size_t vs. unsigned int type mismatch.
>> The loop uses a local unsigned int variable, so adopt that type,
>> matching the header.
>>
>> Fixes: 7a29a869434e ("clk: meson: Add support for Meson clock controller")
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>> drivers/clk/meson/clkc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
[...]
> Also please, CC linux-meson@googlegroups.com on meson related patches.
I used scripts/get_maintainer.pl --nogit-fallback on next-20160111. :)
If there is no in-flight patch I've missed, I can send a patch against
MAINTAINERS to update it with that list address.
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-02-08 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 21:13 [PATCH] clk: meson: Fix meson_clk_register_clks() signature type mismatch Andreas Färber
2016-02-08 8:34 ` Carlo Caione
2016-02-08 8:54 ` Carlo Caione
2016-02-08 10:55 ` Andreas Färber [this message]
2016-02-08 22:15 ` Stephen Boyd
2016-02-08 22:22 ` Andreas Färber
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=56B87430.3040804@suse.de \
--to=afaerber@suse.de \
--cc=carlo@caione.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-meson@googlegroups.com \
--cc=mbrugger@suse.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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).