From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-arch@vger.kernel.org, mturquette@ti.com,
Russell King <linux@arm.linux.org.uk>,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] clkdev: Add default clkdev.h
Date: Tue, 3 Jul 2012 12:48:44 +0100 [thread overview]
Message-ID: <20120703114844.GJ29030@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201207031116.05876.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]
On Tue, Jul 03, 2012 at 11:16:05AM +0000, Arnd Bergmann wrote:
> On Tuesday 03 July 2012, Mark Brown wrote:
> > No idea, I'm just taking the existing default header and making it more
> > generally available.
> I prefer Stephen's version because that maintains the type checking.
I agree, I've already made the change locally.
> However, that is not a controversial point at all IMHO. The question
> that we need to decide on is whether we want automatic "generic-y"
> statements in Kbuild.asm.
Well, it does seem to defeat a large part of the point of having generic
headers if they're not there by default - it means that if you add a
header you need to go round every single architecture adding the header
explicitly which is cumbersome and annoying, especially with the less
actively maintained architectures. On the other hand if you do things
without adding a generic header then people whine about not using the
generic header mechanism...
> I would definitely prefer being able to just write
> generic-y += clkdev.h
I agree but I don't see this as something that should block having the
facility. Or if it does I guess I'll need to try to either fix clkdev
to use the arch include optionally or go round all the architectures
either of which is going to be needlessly painful.
> Maybe Michal Marek or someone on the kbuild mailing list can help
> out with a solution for that.
We could do that incrementally...
The reason I'm doing this is that the lack of a widely available clock
API is a considerable pain point for a lot of the stuff I work on and
this is the major blocker to just enabling the default implementation on
architectures that don't support it already which would be a big step
forwards.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-03 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1341252250-26476-1-git-send-email-broonie@opensource.wolfsonmicro.com>
[not found] ` <20120703120059.f153bd696269528be2baa1bc@canb.auug.org.au>
[not found] ` <20120703101209.GH29030@opensource.wolfsonmicro.com>
2012-07-03 11:16 ` [PATCH] clkdev: Add default clkdev.h Arnd Bergmann
2012-07-03 11:48 ` Mark Brown [this message]
2012-07-03 12:05 ` Stephen Rothwell
2012-07-03 12:33 ` Mark Brown
2012-07-03 13:15 ` Stephen Rothwell
2012-07-03 13:39 ` Arnd Bergmann
2012-07-03 13:47 ` Mark Brown
2012-07-09 22:23 ` Mike Turquette
2012-07-09 23:30 ` Russell King - ARM Linux
2012-07-10 17:22 ` Mark Brown
2012-07-10 18:07 ` Arnd Bergmann
2012-07-11 2:44 ` Paul Mundt
2012-07-11 6:32 ` Arnd Bergmann
[not found] <1341329015-28207-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2012-07-04 8:00 ` Geert Uytterhoeven
2012-07-04 9:22 ` Mark Brown
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=20120703114844.GJ29030@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mmarek@suse.cz \
--cc=mturquette@ti.com \
--cc=sfr@canb.auug.org.au \
/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