From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: linux-omap-2.6 git not updated?
Date: Mon, 17 Aug 2009 10:24:49 +0300 [thread overview]
Message-ID: <20090817072448.GH7278@atomide.com> (raw)
In-Reply-To: <87hbwbhgpq.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [090813 18:32]:
> Tony Lindgren <tony@atomide.com> writes:
>
> > * Tony Lindgren <tony@atomide.com> [090812 16:48]:
> >> * Gadiyar, Anand <gadiyar@ti.com> [090812 16:27]:
> >> > Tony,
> >> >
> >> > Is something wrong with the kernel.org mirror? The last commit
> >> > I see is:
> >> >
> >> > commit 4baadee6e2dd5228e1b17cb5f931c4e0ed8fcb96
> >> > Author: Anand Gadiyar <gadiyar@ti.com>
> >> > Date: Wed Aug 5 16:22:59 2009 +0300
> >> >
> >> > I do see that the other branches (upstream, omap4, ...)
> >> > are updated. Looks like only the master is not yet
> >> > reflecting the patches you applied in the last 7 days.
> >>
> >> Yeah I have not updated master yet with the patches going upstream.
> >> Will reset arch/arm/*omap* in master, and merge in the posted
> >> upstream branches.
> >
> > Updated now with the patches queued for mainline.
> >
>
> Tony,
>
> Can you merge in the .31 fixes branches that RMK has already pulled
> in also? These are the PM fixes from me and Paul's fixes branch.
Those should be all there now. Sounds like we need to rebase our
merge window branches after the fixes go into mainline.
Regards,
Tony
prev parent reply other threads:[~2009-08-17 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 13:27 linux-omap-2.6 git not updated? Gadiyar, Anand
2009-08-12 13:48 ` Tony Lindgren
2009-08-12 17:41 ` Tony Lindgren
2009-08-13 15:32 ` Kevin Hilman
2009-08-17 7:24 ` Tony Lindgren [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=20090817072448.GH7278@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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