From: Felipe Balbi <balbi@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [RFC/PATCH] arm: omap2plus: kill section mismatches
Date: Thu, 7 Apr 2011 11:23:03 +0300 [thread overview]
Message-ID: <20110407082302.GG29038@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <4D9D741D.2040304@ti.com>
On Thu, Apr 07, 2011 at 01:51:49PM +0530, Santosh Shilimkar wrote:
> On 4/7/2011 1:35 PM, Felipe Balbi wrote:
> >Those were very simple to fix and while we should
> >be putting effort on code consolidation, having
> >a noisy compilation is very painful and makes it
> >more difficult to see newer warnings introduced
> >by re-factoring other code.
> >
> >Signed-off-by: Felipe Balbi<balbi@ti.com>
> >---
> I did post one for section mismatch already :)
> http://www.spinics.net/lists/linux-omap/msg49557.html
oops, let's use that one instead :-)
--
balbi
prev parent reply other threads:[~2011-04-07 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 8:05 [RFC/PATCH] arm: omap2plus: kill section mismatches Felipe Balbi
2011-04-07 8:21 ` Santosh Shilimkar
2011-04-07 8:23 ` Felipe Balbi [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=20110407082302.GG29038@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).