From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: Git pull request for omap patches for post 2.6.26
Date: Tue, 8 Jul 2008 10:40:09 +0300 [thread overview]
Message-ID: <20080708074005.GA17594@atomide.com> (raw)
In-Reply-To: <20080707200537.GP29191@flint.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [080707 23:06]:
> On Thu, Jul 03, 2008 at 01:11:42PM +0300, Tony Lindgren wrote:
> > Please pull the omap patches for post-2.6.26 from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap2-upstream
>
> I pulled this some time back but never merged it - but I did look at it.
>
> However, I never got around to looking at your other patches on the
> mailing list I'm afraid.
Yes, I think you've only commented on the patches in the first series
so far. Let me know if you have any comments on the other patches
and I'll fix them ASAP.
Basically once these patches are merged, we're a only missing board-*.c
files under mach-omap2 to be again mostly in sync with mainline tree for
mach-omap2. So hopefully only one more merge window of lots of patches
after this merge window!
Currently plat-omap and mach-omap1 are pretty close in sync with
mainline tree except for some board-*.c under mach-omap1.
> Looking at what's in this git tree, there's at least a number of commits
> early on which are empty. I've not really looked much further.
Looks like there were the two already merged fixed still there, I've
run stg clean on the series and rebased against 2.6.26-rc9. I've also
verified that the series applies against your current tree. The location
to pull from is same as earlier.
> Since I've only just remembered about this, I think I'm going to have to
> say "no more" to further community PXA commits this side of the merge
> window to make sufficient time to look at your OMAP stuff properly.
It would be nice to have merging mach-* patches more distributed so
you don't have to spend so much time looking at that stuff.
Regards,
Tony
next prev parent reply other threads:[~2008-07-08 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 10:11 Git pull request for omap patches for post 2.6.26 Tony Lindgren
2008-07-07 20:05 ` Russell King - ARM Linux
2008-07-08 7:40 ` Tony Lindgren [this message]
2008-07-16 7:18 ` Tony Lindgren
2008-07-16 8:01 ` Tony Lindgren
2008-07-16 8:45 ` Russell King - ARM Linux
2008-07-16 8:57 ` Tony Lindgren
2008-07-16 9:37 ` Russell King - ARM Linux
2008-07-16 14:34 ` Tony Lindgren
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=20080708074005.GA17594@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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