linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org,
	Michael Turquette <mturquette@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tero Kristo <t-kristo@ti.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Liviu Dudau <liviu.dudau@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH 32/35 linux-next] clk: constify of_device_id array
Date: Fri, 27 Mar 2015 00:19:35 -0700	[thread overview]
Message-ID: <20150327071935.GB18059@codeaurora.org> (raw)
In-Reply-To: <386731024.185864.1427020449384.open-xchange@webmail.nmp.proximus.be>

On 03/22, Fabian Frederick wrote:
> 
> 
> > On 18 March 2015 at 15:15 Michael Turquette <mturquette@linaro.org> wrote:
> >
> >
> > Quoting Fabian Frederick (2015-03-16 12:59:06)
> > > of_device_id is always used as const.
> > > (See driver.of_match_table and open firmware functions)
> > >
> > > Signed-off-by: Fabian Frederick <fabf@skynet.be>
> >
> > Acked-by: Michael Turquette <mturquette@linaro.org>
> 
> Thanks :)
> 
> btw, something I forgot to mention in changelog is the __initdata -> __initconst
> for ti_clkdm_match_table[]
> 
> I can send it again with a new changelog if necessary ...
> 

Did you want us to take this through clk-next? If so please
resend with the new commit text.

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

  reply	other threads:[~2015-03-27  7:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 19:17 [PATCH 00/35 linux-next] constify of_device_id array Fabian Frederick
2015-03-16 19:17 ` [PATCH 02/35 linux-next] regulator: " Fabian Frederick
2015-03-17 12:11   ` Mark Brown
2015-03-17 17:10     ` Fabian Frederick
2015-03-17 17:19       ` Mark Brown
2015-03-17 17:26         ` Fabian Frederick
2015-03-19 17:44           ` Mark Brown
     [not found] ` <1426533710-25687-1-git-send-email-fabf@skynet.be>
2015-03-16 19:21   ` [PATCH 21/35 linux-next] mfd: " Fabian Frederick
2015-03-23 12:29     ` Lee Jones
2015-03-16 19:59 ` [PATCH 32/35 linux-next] clk: " Fabian Frederick
2015-03-18 14:15   ` Michael Turquette
2015-03-22 10:34     ` Fabian Frederick
2015-03-27  7:19       ` Stephen Boyd [this message]
2015-03-31 19:05         ` Fabian Frederick

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=20150327071935.GB18059@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=fabf@skynet.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mturquette@linaro.org \
    --cc=sudeep.holla@arm.com \
    --cc=t-kristo@ti.com \
    /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).