linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clkdev: Add default clkdev.h
Date: Mon, 14 May 2012 20:09:28 +0100	[thread overview]
Message-ID: <20120514190928.GJ25668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201205141903.04121.arnd@arndb.de>

On Mon, May 14, 2012 at 07:03:03PM +0000, Arnd Bergmann wrote:

> I'm not completely sure about this part. It should work just fine, but
> we haven't done this for any of the other asm/* headers. If we decide
> to list generic header files  in Kconfig.asm that automatically get
> added to architectures, I would prefer doing it with a nicer syntax so
> we can do it for a lot of the other header files too. For now, I'd
> prefer to just add the file manually to the asm/Kbuild files in the
> architectures where it makes sense (e.g. all but s390).

The problem with that is the general pain that seems to come from trying
to get all the architecture maintainers to apply patches like this (lots
of them are OK but many do great /dev/null impressions) and it's pushing
the problem back onto the wrong people.  It seems less work to go put
something ugly in and then hopefully some Kbuild expert will get annoyed
and fix things rather than we get stuck with the status quo.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120514/8cd3ea98/attachment-0001.sig>

      reply	other threads:[~2012-05-14 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 14:19 [PATCH] clkdev: Add default clkdev.h Mark Brown
2012-05-14 19:03 ` Arnd Bergmann
2012-05-14 19:09   ` Mark Brown [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=20120514190928.GJ25668@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).