From: Tony Lindgren <tony@atomide.com>
To: "Luís Cargnini" <lvcargnini@gmail.com>
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH RFC] arch/arm/plat-omap/devices.c
Date: Tue, 18 Sep 2007 15:11:44 -0700 [thread overview]
Message-ID: <20070918221143.GG2521@atomide.com> (raw)
In-Reply-To: <ae36f8040709181333q2b8e3e6ena5d864b14178c582@mail.gmail.com>
Hi,
* Luís Cargnini <lvcargnini@gmail.com> [070918 13:34]:
> --- linux-omap-2.6/arch/arm/plat-omap/devices.c 2007-08-28 01:01:
> 50.502065325 -0300
> +++ linux-omap-2.6.23-instramed/arch/arm/plat-omap/devices.c 2007-09-18
> 15:05:44.748685528 -0300
> @@ -25,6 +25,26 @@
> #include <asm/arch/gpio.h>
> #include <asm/arch/menelaus.h>
>
> +/*-------------------------------------------------------------------------*/
> +/**
> + * 18/09/2007 - 14:35 - 03:00GMT
> + * lvcargnini@ieee.org
> + * Luis Vitorio modifications for devices.c
> + * added this to fix some bugs founded for mmc and possible speed-up
> + * enhancements removing unecessary code, for some plataforms
> + * why test if cpu_is_2420 on the fly ????
> + */
> +
> +#if defined(CONFIG_ARCH_OMAP16XX)
> +#include <asm/arch/omap16xx.h>
> +#elif defined(CONFIG_ARCH_OMAP24XX)
> +#include <asm/arch/omap24xx.h>
> +#elif defined(CONFIG_ARCH_OMAP34XX)
> +#include <asm/arch/omap34xx.h>
> +#endif
> +
> +/*-------------------------------------------------------------------------*/
> +
> #if defined(CONFIG_OMAP_DSP) || defined(CONFIG_OMAP_DSP_MODULE)
>
> #include "../plat-omap/dsp/dsp_common.h"
We should just include all the headers we need, no need to ifdef them
out.
There are no real reasons why we could not compile in all the omap
kernels into one binary now that gcc supports mixing in later assembly
code. Adding ifdefs there will make compiling in support for various
omaps harder. (We can already compile in 15xx and 16xx).
Please also leave out changelog type comments, they will show up in
the git repository. Also leave out any formatting changes, they make
it harder to see what you're fixing. See the following under
Documentation in your Linux tree:
Documentation/SubmittingPatches
Documentation/SubmittingDrivers
Documentation/SubmitChecklist
Regards,
Tony
next prev parent reply other threads:[~2007-09-18 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 20:33 [PATCH RFC] arch/arm/plat-omap/devices.c Luís Cargnini
2007-09-18 22:11 ` Tony Lindgren [this message]
2007-09-19 1:44 ` Luís Cargnini
2007-09-19 15:49 ` Dirk Behme
2007-10-01 18:06 ` Tony Lindgren
2007-10-01 23:20 ` Luís Cargnini
2007-10-02 0:01 ` Tony Lindgren
[not found] ` <ae36f8040710011707u34b21a1dx1e63db8c7bd85c9d@mail.gmail.com>
[not found] ` <ae36f8040710011710w50e766c3ve10cded27a6e0689@mail.gmail.com>
2007-10-02 0:10 ` Fwd: " Luís Cargnini
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=20070918221143.GG2521@atomide.com \
--to=tony@atomide.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=lvcargnini@gmail.com \
/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