From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Ameya Palande <ameya.palande@nokia.com>,
"Guzman Lugo, Fernando" <x0095840@ti.com>,
"Kanigeri, Hari" <h-kanigeri2@ti.com>,
Omar Ramirez Luna <omar.ramirez@hotmail.com>
Subject: Re: [PATCH 1/2] DSPBRIDGE: Remove autoconf.h dependency from host_os header
Date: Tue, 23 Mar 2010 12:28:22 -0500 [thread overview]
Message-ID: <4BA8FA36.2030609@ti.com> (raw)
In-Reply-To: <1268949429-30368-2-git-send-email-omar.ramirez@ti.com>
On 3/18/2010 4:57 PM, Ramirez Luna, Omar wrote:
> There shouldn't be any dependency on the definitions generated
> by autoconf.h, besides it is automatically included by the
> build system.
>
> This solves the following warning:
>
> In file included from arch/arm/plat-omap/include/dspbridge/host_os.h:20,
> from arch/arm/mach-omap2/io.c:51:
> include/linux/autoconf.h:165:1: warning: "CONFIG_DEFAULT_IOSCHED" redefined
> In file included from<command-line>:0:
> ./include/generated/autoconf.h:172:1: warning: this is the location of the previous definition
>
> Signed-off-by: Omar Ramirez Luna<omar.ramirez@hotmail.com>
> ---
> arch/arm/plat-omap/include/dspbridge/host_os.h | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
Pushed to dspbridge.
- omar
prev parent reply other threads:[~2010-03-23 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 21:57 [PATCH 0/2] dspbridge: 2.6.33 migration patches Omar Ramirez Luna
2010-03-18 21:57 ` [PATCH 1/2] DSPBRIDGE: Remove autoconf.h dependency from host_os header Omar Ramirez Luna
2010-03-18 21:57 ` [PATCH 2/2] DSPBRIDGE: Fix header locations mach to plat Omar Ramirez Luna
2010-03-23 17:28 ` Omar Ramirez Luna
2010-03-23 17:28 ` Omar Ramirez Luna [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=4BA8FA36.2030609@ti.com \
--to=omar.ramirez@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@hotmail.com \
--cc=x0095840@ti.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