public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 11:16:05 +0000	[thread overview]
Message-ID: <201207031116.05876.arnd@arndb.de> (raw)
In-Reply-To: <20120703101209.GH29030@opensource.wolfsonmicro.com>

On Tuesday 03 July 2012, Mark Brown wrote:
> On Tue, Jul 03, 2012 at 12:00:59PM +1000, Stephen Rothwell wrote:
> > On Mon,  2 Jul 2012 19:04:10 +0100 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> 
> > > +#define __clk_get(clk)     ({ 1; })
> > > +#define __clk_put(clk)     do { } while (0)
> 
> > So why not:
> 
> > struct clk;
> 
> > static inline int __clk_get(struct clk *clk) { return 1; }
> > static inline void __clk_put(struct clk *clk) ( )
> 
> 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.
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.

I'm not opposed to the idea, but I can imagine some arch maintainers
fine it confusing. When you first posted the patch, I spent some
time trying to get the wildcard logic moved to scripts/Makefile.asm-generic
and scripts/Makefile.headersinst but couldn't figure it out in the end.

I would definitely prefer being able to just write 

generic-y += clkdev.h 

in include/asm-generic/Kbuild.asm, rather than 

ifeq ($(wildcard $(srctree)/arch/$(SRCARCH)/include/asm/clkdev.h),)
generic-y += clkdev.h
endif

Maybe Michal Marek or someone on the kbuild mailing list can help
out with a solution for that.

	Arnd

       reply	other threads:[~2012-07-03 11:16 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     ` Arnd Bergmann [this message]
2012-07-03 11:48       ` [PATCH] clkdev: Add default clkdev.h Mark Brown
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=201207031116.05876.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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