From: "Heiko Stübner" <heiko@sntech.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Ben Dooks <ben-linux@fluff.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] S3C2443: Move i2s clock definitions to common code
Date: Sun, 21 Aug 2011 19:25:04 +0200 [thread overview]
Message-ID: <201108211925.05300.heiko@sntech.de> (raw)
In-Reply-To: <20110821171332.GF28546@n2100.arm.linux.org.uk>
Am Sonntag 21 August 2011, 19:13:32 schrieb Russell King - ARM Linux:
> On Sat, Aug 20, 2011 at 06:01:29PM +0200, Heiko Stübner wrote:
> > +/* i2s-ref
> > + *
> > + * i2s bus reference clock, selectable from external, esysclk or epllref
> > + *
> > + * Note, this used to be two clocks, but was compressed into one.
> > +*/
> > +
> > +struct clk *clk_i2s_srclist[] = {
> > + [0] = &clk_i2s_eplldiv.clk,
> > + [1] = &clk_i2s_ext,
> > + [2] = &clk_epllref.clk,
> > + [3] = &clk_epllref.clk,
> > +};
>
> Is there any reason not to make this static (have you run your patch
> through checkpatch.pl ?)
Yep I did run all of them through checkpatch (after beeing scolded last time)
and it didn't report anything.
But for this move of code I simply grabbed the code fragments and put them
into their new location (i.e. it was this way in mach-s3c2443/clock.c) and
should have probably taken a closer look at what I'm moving.
So it seems you are right, it should probably be static as everything else is
also static.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] S3C2443: Move i2s clock definitions to common code
Date: Sun, 21 Aug 2011 19:25:04 +0200 [thread overview]
Message-ID: <201108211925.05300.heiko@sntech.de> (raw)
In-Reply-To: <20110821171332.GF28546@n2100.arm.linux.org.uk>
Am Sonntag 21 August 2011, 19:13:32 schrieb Russell King - ARM Linux:
> On Sat, Aug 20, 2011 at 06:01:29PM +0200, Heiko St?bner wrote:
> > +/* i2s-ref
> > + *
> > + * i2s bus reference clock, selectable from external, esysclk or epllref
> > + *
> > + * Note, this used to be two clocks, but was compressed into one.
> > +*/
> > +
> > +struct clk *clk_i2s_srclist[] = {
> > + [0] = &clk_i2s_eplldiv.clk,
> > + [1] = &clk_i2s_ext,
> > + [2] = &clk_epllref.clk,
> > + [3] = &clk_epllref.clk,
> > +};
>
> Is there any reason not to make this static (have you run your patch
> through checkpatch.pl ?)
Yep I did run all of them through checkpatch (after beeing scolded last time)
and it didn't report anything.
But for this move of code I simply grabbed the code fragments and put them
into their new location (i.e. it was this way in mach-s3c2443/clock.c) and
should have probably taken a closer look at what I'm moving.
So it seems you are right, it should probably be static as everything else is
also static.
Heiko
next prev parent reply other threads:[~2011-08-21 17:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 15:57 [PATCH 0/4] S3C2416: Enable IIS and HSSPI clocks Heiko Stübner
2011-08-20 15:57 ` Heiko Stübner
2011-08-20 16:01 ` [PATCH 1/4] S3C2443: Move i2s clock definitions to common code Heiko Stübner
2011-08-20 16:01 ` Heiko Stübner
2011-08-21 17:13 ` Russell King - ARM Linux
2011-08-21 17:13 ` Russell King - ARM Linux
2011-08-21 17:25 ` Heiko Stübner [this message]
2011-08-21 17:25 ` Heiko Stübner
2011-08-21 20:26 ` Marek Vasut
2011-08-21 20:26 ` Marek Vasut
2011-08-21 21:11 ` Heiko Stübner
2011-08-21 21:11 ` Heiko Stübner
2011-08-23 3:42 ` Kukjin Kim
2011-08-23 3:42 ` Kukjin Kim
2011-08-23 20:28 ` Heiko Stübner
2011-08-23 20:28 ` Heiko Stübner
2011-08-20 16:02 ` [PATCH 2/4] S3C2443: Define constant for HSSPI pclk Heiko Stübner
2011-08-20 16:02 ` Heiko Stübner
2011-08-20 16:03 ` [PATCH 3/4] S3C2416: Add HSSPI clock sourced from EPLL Heiko Stübner
2011-08-20 16:03 ` Heiko Stübner
2011-08-20 16:03 ` [PATCH 4/4] S3C2443: Add hsspi-clock from pclk Heiko Stübner
2011-08-20 16:03 ` Heiko Stübner
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=201108211925.05300.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.