linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] at91 : move pm.h header to arch/arm/include/asm
Date: Mon, 9 Jan 2012 11:29:20 +0000	[thread overview]
Message-ID: <20120109112920.GJ21765@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4F0ACD35.1000600@linaro.org>

On Mon, Jan 09, 2012 at 12:19:17PM +0100, Daniel Lezcano wrote:
> Actually, the header moves from :
> 
> 	arch/arm/mach-at91/pm.h
> to:
> 	arch/arm/include/asm/at91_pm.h.
> 
> This place and the renaming of the file complies with the comments of
> Russell,

No it doesn't.  There's absolutely no way in hell I want arch/arm/include/asm
to be littered with hundreds of crappy platform specific header files.

  reply	other threads:[~2012-01-09 11:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 15:48 [PATCH 1/2] at91 : move pm.h header to arch/arm/include/asm Daniel Lezcano
2012-01-06 15:48 ` [PATCH 2/2] at91 : move cpuidle driver to drivers/cpuidle directory Daniel Lezcano
2012-01-06 17:30 ` [PATCH 1/2] at91 : move pm.h header to arch/arm/include/asm Arnd Bergmann
2012-01-06 23:19   ` Daniel Lezcano
2012-01-09 11:19   ` Daniel Lezcano
2012-01-09 11:29     ` Russell King - ARM Linux [this message]
2012-01-09 13:54       ` Daniel Lezcano
2012-01-09 14:44         ` Russell King - ARM Linux
2012-01-09 15:00           ` Daniel Lezcano
2012-01-09 16:48           ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-09 17:09             ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-09 17:41               ` Nicolas Ferre
2012-01-09 14:46         ` Rob Herring
2012-01-09 15:08           ` Daniel Lezcano
2012-01-07 10:45 ` Jean-Christophe PLAGNIOL-VILLARD

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=20120109112920.GJ21765@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).