linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] clk: tegra: Fix duplicate const for parent names
Date: Thu, 9 Apr 2015 08:28:26 -0700	[thread overview]
Message-ID: <20150409152826.GB18835@codeaurora.org> (raw)
In-Reply-To: <20150409101947.GM12103@ulmo>

On 04/09, Thierry Reding wrote:
> On Thu, Apr 09, 2015 at 12:07:59PM +0200, Krzysztof Kozlowski wrote:
> > 2015-04-09 12:00 GMT+02:00 Thierry Reding <thierry.reding@gmail.com>:
> > > On Wed, Apr 08, 2015 at 03:22:15PM +0200, Krzysztof Kozlowski wrote:
> > >> Replace duplicated const keyword for 'emc_parent_clk_names' with proper
> > >> array of const pointers to const strings.
> > >>
> > >> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > >> ---
> > >>  drivers/clk/tegra/clk-emc.c | 2 +-
> > >>  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > This would probably better go in via the Tegra tree since the patch that
> > > contains this has only made it to linux-next.
> > >
> > > Stephen, Mike, any objections to me taking this?
> > 
> > Applying this without the change for const-ness of parent_names (patch
> > by Sascha Hauer sent before mine [1]) would introduce a warning -
> > assign of const to non-const. Any idea to solve it? Immutable branch?
> 
> Right, I had missed that. Immutable branch would work, though perhaps
> it'd be easier to just defer this until after v4.1-rc1. The warning
> shouldn't happen if we leave out this single patch and apply it later
> on, right?
> 
> Alternatively the whole series could be deferred until after v4.1-rc1.
> 

Yeah I don't really care to make an immutable branch for this
cleanup series. If everyone is ok with waiting until after -rc1
we can apply the Tegra patch then (or you can and we'll get it
through a pull later). We should be able to apply the parts that
go through clk tree though.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2015-04-09 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 13:22 [PATCH 0/8] clk: Minor cleanups Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 1/8] clk: rockchip: Staticize file-scope declarations Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 2/8] clk: exynos: " Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 3/8] clk: Constify pointers to parent names in init data Krzysztof Kozlowski
2015-04-08 23:36   ` Stephen Boyd
2015-04-09  7:23     ` Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 4/8] clk: tegra: Fix duplicate const for parent names Krzysztof Kozlowski
2015-04-09 10:00   ` Thierry Reding
2015-04-09 10:07     ` Krzysztof Kozlowski
2015-04-09 10:19       ` Thierry Reding
2015-04-09 10:33         ` Krzysztof Kozlowski
2015-04-09 15:28         ` Stephen Boyd [this message]
2015-04-08 13:22 ` [PATCH 5/8] clk: cdce706: Constify parent names in clock init data Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 6/8] clk: sirf: " Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 7/8] clk: ls1x: Fix duplicate const for parent names Krzysztof Kozlowski
2015-04-08 13:22 ` [PATCH 8/8] MIPS: Alchemy: Remove unneeded cast removing const Krzysztof Kozlowski

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=20150409152826.GB18835@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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).