From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Russell King <linux@arm.linux.org.uk>,
mturquette@ti.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] clkdev: Add default clkdev.h
Date: Wed, 4 Jul 2012 10:22:56 +0100 [thread overview]
Message-ID: <20120704092255.GA4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAMuHMdXzE48MCpQWjaxdrYMEwi-Cn5GR6NYrDAOAKwqiJ3m7Yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Wed, Jul 04, 2012 at 10:00:50AM +0200, Geert Uytterhoeven wrote:
> Quoting Sam:
> "Any use of wildcards in include/asm-generic/Kbuild.asm is bogus."
> http://lkml.indiana.edu/hypermail/linux/kernel/1206.2/01507.html
Without actually explaining why which isn't terribly helpful :/
As far as I can tell it looks like this is for headers which may
optionally be absent but clkdev.h is a header which should never be
absent, either the architecture defines it or it uses the generic one.
As I said further up the thread having to go round ever single
architecture and get them to actually apply patches for stuff like this
is needlessly painful.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-04 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 15:23 [PATCH] clkdev: Add default clkdev.h Mark Brown
2012-07-03 15:29 ` Stephen Rothwell
2012-07-04 8:00 ` Geert Uytterhoeven
2012-07-04 9:22 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-05 4:04 Mark Brown
2012-08-28 18:56 Mark Brown
2012-08-25 18:16 Mark Brown
2012-07-03 17:04 Mark Brown
2012-07-03 22:07 ` Stephen Rothwell
2012-06-14 11: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=20120704092255.GA4111@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@ti.com \
--cc=sam@ravnborg.org \
--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;
as well as URLs for NNTP newsgroup(s).