From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Sanjeev Premi <premi@ti.com>,
linux-omap Mailing List <linux-omap@vger.kernel.org>
Subject: RE: Errors when building for omap4 only
Date: Thu, 6 Jan 2011 19:32:09 +0530 [thread overview]
Message-ID: <23f6ffb3d1a6ddd06de44cd77764c680@mail.gmail.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930248201A31@dbde02.ent.ti.com>
> -----Original Message-----
> From: Premi, Sanjeev [mailto:premi@ti.com]
> Sent: Thursday, January 06, 2011 7:26 PM
> To: Shilimkar, Santosh; linux-omap Mailing List
> Subject: RE: Errors when building for omap4 only
>
>
>
> > -----Original Message-----
> > From: Shilimkar, Santosh
> > Sent: Thursday, January 06, 2011 7:19 PM
> > To: Premi, Sanjeev; linux-omap Mailing List
> > Subject: RE: Errors when building for omap4 only
> >
> > Sanjeev,
> > > -----Original Message-----
> > > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > > owner@vger.kernel.org] On Behalf Of Premi, Sanjeev
> > > Sent: Thursday, January 06, 2011 6:18 PM
> > > To: linux-omap Mailing List
> > > Subject: Errors when building for omap4 only
> > >
> > > Hi all,
> > >
> > > I was trying to build OMAP4 only kernel from the linux-omap
> master.
> > > Came across few failures caused by exclusion of OMAP3/3 specific
> > > code via #ifdef.
> > >
> > These are addressed already. You could look at below series
> > http://www.mail-archive.com/linux-
> omap@vger.kernel.org/msg41712.html
> >
>
> Great! I missed the series.
>
> Question (after quick browse): Don't addition stubs add too many
> strings to the code?
>
They do. But we want these functions to throw warning when they are
used on wrong SOCS. So that wrong usage is avoided and if exist can
be killed.
prev parent reply other threads:[~2011-01-06 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 12:48 Errors when building for omap4 only Premi, Sanjeev
2011-01-06 13:49 ` Santosh Shilimkar
2011-01-06 13:55 ` Premi, Sanjeev
2011-01-06 14:02 ` Santosh Shilimkar [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=23f6ffb3d1a6ddd06de44cd77764c680@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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