linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap2 sparse fixes
Date: Tue, 28 Sep 2010 11:31:59 -0700	[thread overview]
Message-ID: <20100928183157.GH3117@atomide.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402DB3F94C9@dbde02.ent.ti.com>

* G, Manjunath Kondaiah <manjugk@ti.com> [100928 08:26]:
> 
> 
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony at atomide.com] 
> > Sent: Tuesday, September 28, 2010 8:52 PM
> > To: G, Manjunath Kondaiah
> > Cc: linux-omap at vger.kernel.org; 
> > linux-arm-kernel at lists.infradead.org; Samuel Ortiz; Dmitry 
> > Torokhov; linux-mtd at lists.infradead.org; Russell King - ARM Linux
> > Subject: Re: [GIT PULL] omap2 sparse fixes
> > 
> > * G, Manjunath Kondaiah <manjugk@ti.com> [100928 01:04]:
> > > 
> > > Three patches are fixed using above method which are:
> > > OMAP: mach-omap2: Fix static function warnings
> > > OMAP: plat-omap: Fix static function warnings TWL IRQ: Fix fucntion 
> > > declaration warnings
> > 
> > OK thanks.
> >  
> > > are available in the git repository at:
> > > 
> > >   git://dev.omapzoom.org/pub/scm/manju/kernel-omap3-dev.git 
> > > sparse_fixes_v3
> > > 
> > > G, Manjunath Kondaiah (10):
> > >       OMAP: mach-omap2: Fix incorrect assignment warnings
> > >       OMAP: mach-omap2: Fix static declaration warnings
> > >       OMAP2plus: Fix static function warnings
> > >       OMAP: mach-omap2: Fix miscellaneous sparse warnings
> > >       OMAP: plat-omap: Fix static function warnings
> > >       OMAP: NAND: Fix static declaration warning
> > >       TWL CORE: Fix sparse warning
> > >       TWL IRQ: Fix fucntion declaration warnings
> > 
> > Didn't Samuel just reply that he has applied these two TWL fixes?
> 
> Samuel applied only one patch and other patch is yet to be applied.
> Do you want me to pull out these two twl patches from the series?

Yes please take out all patches that are not in arch/arm/*omap*/ path.
The others really should go to the driver maintainers.

Tony

  reply	other threads:[~2010-09-28 18:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  8:56 [GIT PULL] omap2 sparse fixes G, Manjunath Kondaiah
2010-09-23 22:58 ` Tony Lindgren
2010-09-24 19:43   ` G, Manjunath Kondaiah
2010-09-25  0:19     ` Tony Lindgren
2010-09-25  6:21       ` G, Manjunath Kondaiah
2010-09-27 13:41       ` G, Manjunath Kondaiah
2010-09-27 14:07         ` Russell King - ARM Linux
2010-09-27 15:00           ` G, Manjunath Kondaiah
2010-09-28  8:12       ` G, Manjunath Kondaiah
2010-09-28 15:21         ` Tony Lindgren
2010-09-28 15:35           ` G, Manjunath Kondaiah
2010-09-28 18:31             ` Tony Lindgren [this message]
2010-09-29 19:51               ` G, Manjunath Kondaiah
2010-09-29 21:56                 ` Tony Lindgren
2010-09-29 23:46                   ` G, Manjunath Kondaiah
2010-10-05  2:14                     ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2010-09-22  8:49 G, Manjunath Kondaiah

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=20100928183157.GH3117@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).