From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Munegowda, Keshava" <keshava_mgowda@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH V2]omap: mux.c warning removal
Date: Mon, 10 May 2010 15:30:29 -0700 [thread overview]
Message-ID: <20100510223029.GL16460@atomide.com> (raw)
In-Reply-To: <874oiflos4.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [100510 09:07]:
> "Munegowda, Keshava" <keshava_mgowda@ti.com> writes:
>
> > From: Keshava Munegowda <a0393220@ti.com>
> >
> > This patch removes the below warning
> > arch/arm/mach-omap2/mux.c:52: warning: 'mux_phys' defined but not used
> > The definition of variable mux_phys should be enclosed in the macro CONFIG_ARCH_OMAP3
> >
> > Signed-off-by: Keshava Munegowda <a0393220@ti.com>
>
> Thanks, this version looks better.
Nothing wrong with this patch. But it will need to be reverted
as soon as omap24xx mux code is updated. And that's going to
happen as soon as I have a chance.
So let's just keep the warning for now.
Regards,
Tony
next prev parent reply other threads:[~2010-05-10 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 6:47 [PATCH V2]omap: mux.c warning removal Munegowda, Keshava
2010-05-10 16:11 ` Kevin Hilman
2010-05-10 22:30 ` Tony Lindgren [this message]
2010-05-11 10:30 ` Munegowda, Keshava
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=20100510223029.GL16460@atomide.com \
--to=tony@atomide.com \
--cc=keshava_mgowda@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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