linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] at91 : move pm.h header to arch/arm/include/asm
Date: Mon, 09 Jan 2012 14:54:32 +0100	[thread overview]
Message-ID: <4F0AF198.1030803@linaro.org> (raw)
In-Reply-To: <20120109112920.GJ21765@n2100.arm.linux.org.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/09/2012 12:29 PM, Russell King - ARM Linux wrote:
> 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.

Ok. Actually there are 9 pm.h files but I agree with a domino effect we
can have more header files brought to this directory like "control.h",
"powerdomain.h", etc ...

Does it make sense to merge all the pm.h file in a single pm.h which
will be located in arch/arm/include/asm ?

And we separate the different archs specific with #ifdef
CONFIG_ARCH_AT91, CONFIG_ARCH_OMAP, etc ...

The resulting file will be bigger but that will be easier to find a
pattern we can factor out in the header file and that will encourage the
developers to share the code across the different arch.

Thanks
  -- Daniel

- -- 
 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPCvGYAAoJEAKBbMCpUGYAGTMH/iLSep3kiUfxJiDLlxLoPkcs
pyvJGnD/leJOvykxd6QQ3dCs+4i2tbYnMEGVtfYWbTHOraOTa1u5oRcS/F0yNOYu
kifKYyLKJPT9lkYlaDBU9/cWZDhHdAQpu+2vKnVDIJLeSwBDxCEROoPQaWGs2cnw
0k06iCE/Zq9V5duFE/u7n0RX7XpJCLmdMcRDRw2GW7WuZ6DA2BeU2MEFudQ1NLK1
bB9zyVVCBxPVVdqjgaSagU0LTCPUeHALsYQVUqpPYMuYK30/ACyakyA/jLFn52lD
x47ybOuLOGSl4c0/wS1duCBbIFNYsT/kBcVXFXA/usAaCjW12H7OV+9MEA7lB8E=
=y5HS
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-01-09 13:54 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
2012-01-09 13:54       ` Daniel Lezcano [this message]
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=4F0AF198.1030803@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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).