From: Tony Lindgren <tony@atomide.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] omap2 sparse fixes
Date: Thu, 23 Sep 2010 15:58:52 -0700 [thread overview]
Message-ID: <20100923225851.GR4211@atomide.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402785A390E@dbde02.ent.ti.com>
* G, Manjunath Kondaiah <manjugk@ti.com> [100922 01:48]:
> Hi Tony,
>
> Please pull omap2 sparse fixes from:
>
> git://dev.omapzoom.org/pub/scm/manju/kernel-omap3-dev.git sparse_fixes
>
> Regards,
> Manjunath
>
>
> The following changes since commit 8b15575cae7a93a784c3005c42b069edd9ba64dd:
> Sage Weil (1):
> fs: {lock,unlock}_flocks() stubs to prepare for BKL removal
>
> are available in the git repository at:
>
> git://dev.omapzoom.org/pub/scm/manju/kernel-omap3-dev.git sparse_fixes
>
> G, Manjunath Kondaiah (10):
> OMAP: mach-omap2: Fix incorrect assignment warnings
> OMAP: mach-omap2: Fix static declaration warnings
> OMAP: mach-omap2: 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
> OMAP2/3: Convert write/read functions to raw read/write
> OMAP3: Keypad: Fix incorrect type initializer
Manjunath, this looks safe to pull, however one request though:
Can you please rebase it on v2.6.35 or v2.6.36-rc5?
Now your branch is on some commit after the -rc5 tag.
It's better to base branches at the most recent stable tag
(v2.6.35) or a recent -rc tag (v2.6.36-rc5).
Otherwise we end up moving our linux-omap tree forward too unless
I use git pull --rebase option.. I've updated the elinux.org wiki
instructions for that too, sorry if the earlier instructions there
were a bit unclear.
Thanks,
Tony
next prev parent reply other threads:[~2010-09-23 22:58 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 [this message]
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
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=20100923225851.GR4211@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@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;
as well as URLs for NNTP newsgroup(s).