public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: "Gadiyar, Anand" <gadiyar-l0cyMroinI0@public.gmane.org>,
	Felipe Balbi
	<felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>,
	"gregkh-l3A5Bk7waGM@public.gmane.org"
	<gregkh-l3A5Bk7waGM@public.gmane.org>,
	"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] usb: ehci-omap: Update platform header file path
Date: Wed, 25 Nov 2009 10:06:27 -0800	[thread overview]
Message-ID: <20091125180627.GF4348@atomide.com> (raw)
In-Reply-To: <20091125091456.GA30595-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>

* Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org> [091125 01:13]:
> On Wed, Nov 25, 2009 at 02:35:56PM +0530, Gadiyar, Anand wrote:
> > Olof Johansson wrote:
> > > 
> > > The OMAP usb header file has moved, update the driver so it 
> > > will build.
> > > 
> > > Signed-off-by: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
> > > 
> > > ---
> > > 
> > > Greg, any chance you can just ack this so Tony can merge it through his
> > > tree for .33? The header files changes in question are going in through
> > > that tree.
> > > 
> > 
> > I believe it has already been taken care of in Tony's for-next?
> 
> Oh, weird. Looking at the history of the file on git.kernel.org:
> 
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=history;f=drivers/usb/host/ehci-omap.c;hb=HEAD
> 
> It shows Tony making the change on Oct 30, and then 4 fresh merges of
> the driver? That's odd.

Yeah those duplicate commits happen when we rebuild the linux-omap
tree on a new -rc. That's when all the development and testing
branches get merged back in again.

To keep the linux-omap tree pullable all the time, we rebuild 
the linux-omap tree periodically with something like this:

$ git checkout -b tmp-rebuild-1258915893 linus
$ git merge -m "Merge omap-testing" omap-testing
$ git merge -m "Merge for-next" for-next
$ git merge -m "Merge cbus" cbus
$ git merge -s ours master
$ git checkout master
$ git merge tmp-rebuild-1258915893

What I've queued up is in for-next branch, omap-testing and
cbus are just development branches that may get rebased as
needed. And master branch is what people are using for omap
to test things, and that stays pullable.

As we currently carry the ehci-omap patch in omap-testing branch,
it shows up as a merge every time we rebuild. These duplicate
commits will disappear once the echi-omap gets merged to Linus'
tree.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-11-25 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25  9:02 [PATCH] usb: ehci-omap: Update platform header file path Olof Johansson
2009-11-25  9:05 ` Gadiyar, Anand
     [not found]   ` <5A47E75E594F054BAF48C5E4FC4B92AB030AAC2D5A-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-11-25  9:08     ` Olof Johansson
2009-11-25  9:14     ` Olof Johansson
     [not found]       ` <20091125091456.GA30595-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
2009-11-25 18:06         ` Tony Lindgren [this message]
2009-11-25 12:53 ` Greg KH
     [not found]   ` <20091125125326.GA18175-l3A5Bk7waGM@public.gmane.org>
2009-11-25 17:57     ` Tony Lindgren
     [not found]       ` <20091125175739.GE4348-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-12-04  2:23         ` Olof Johansson
     [not found]           ` <20091204022357.GA19315-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
2009-12-15 21:25             ` 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=20091125180627.GF4348@atomide.com \
    --to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
    --cc=felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
    --cc=gadiyar-l0cyMroinI0@public.gmane.org \
    --cc=gregkh-l3A5Bk7waGM@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.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