From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC][PATCH 1/8] sh: clock-sh7724: add CLKDEV_ICK_ID for cleanup
Date: Wed, 06 Jul 2011 01:40:21 +0000 [thread overview]
Message-ID: <20110706014021.GE24169@linux-sh.org> (raw)
In-Reply-To: <87tyb0jjge.wl%kuninori.morimoto.gx@renesas.com>
On Wed, Jul 06, 2011 at 10:28:30AM +0900, kuninori.morimoto.gx@renesas.com wrote:
> > On Tue, Jul 05, 2011 at 06:17:55PM -0700, Kuninori Morimoto wrote:
> > > diff --git a/arch/sh/kernel/cpu/sh4a/clock-sh7724.c b/arch/sh/kernel/cpu/sh4a/clock-sh7724.c
> > > index 77bcef5..0891876 100644
> > > --- a/arch/sh/kernel/cpu/sh4a/clock-sh7724.c
> > > +++ b/arch/sh/kernel/cpu/sh4a/clock-sh7724.c
> > > @@ -254,6 +254,7 @@ static struct clk mstp_clks[HWBLK_NR] = {
> > >
> > > #define CLKDEV_CON_ID(_id, _clk) { .con_id = _id, .clk = _clk }
> > > #define CLKDEV_DEV_ID(_id, _clk) { .dev_id = _id, .clk = _clk }
> > > +#define CLKDEV_ICK_ID(_cid, _did, _clk) { .con_id = _cid, .dev_id = _did, .clk = _clk }
> > >
> > > static struct clk_lookup lookups[] = {
> > > /* main clocks */
> >
> > Perhaps while we're at it, it would help to move these macros in to
> > sh_clk.h.
>
> OK.
>
> Can I send incremental patch which name will be "move CLKDDEV_XXX_ID macro to sh_clk.h"
> or v2 patch set ?
>
Incremental patch sounds good. I'll queue this series up as it is, as
it's a reasonable cleanup.
prev parent reply other threads:[~2011-07-06 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 1:17 [RFC][PATCH 1/8] sh: clock-sh7724: add CLKDEV_ICK_ID for cleanup Kuninori Morimoto
2011-07-06 1:24 ` Paul Mundt
2011-07-06 1:28 ` kuninori.morimoto.gx
2011-07-06 1:40 ` Paul Mundt [this message]
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=20110706014021.GE24169@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.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