From: Tony Lindgren <tony@atomide.com>
To: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: linux-omap@vger.kernel.org, x00omar@ti.com,
vikram.pandita@ti.com, h-kanigeri2@ti.com
Subject: Re: [FYI] Rebase: tidspbridge-20081118
Date: Thu, 20 Nov 2008 09:29:11 -0800 [thread overview]
Message-ID: <20081120172910.GJ4927@atomide.com> (raw)
In-Reply-To: <20081120.102114.116290435.Hiroshi.DOYU@nokia.com>
* Hiroshi DOYU <Hiroshi.DOYU@nokia.com> [081120 00:21]:
> From: "ext Tony Lindgren" <tony@atomide.com>
> Subject: Re: [FYI] Rebase: tidspbridge-20081118
> Date: Wed, 19 Nov 2008 13:37:29 -0800
>
> > * Hiroshi DOYU <Hiroshi.DOYU@nokia.com> [081117 05:37]:
> > > Hi,
> > >
> > > The following changes since commit f23f23fb6bfd8ce4669070df35ec9b320983ac0c:
> > > Grazvydas Ignotas (1):
> > > HSMMC: Add MMC configuration for pandora
> > >
> > > are available in the git repository at:
> > >
> > > http://git.gitorious.org/lk/mainline.git tidspbridge-20081118
> >
> > Great, I'm now also mirroring tidspbridge-20081118 branch at:
> >
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary
>
> Since I think that logical patchset doesn't make sense for this early
> stage, I am considering to stop rebasing on the top of "omap/master"
> and to start updating "tidspbridge", just merging "omap/master" into
> it frequently.
Sure, looks like it's going to be a quite a while before the bridge
code is a logical patchset :)
Tony
prev parent reply other threads:[~2008-11-20 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 2:14 [PATCH 5/5][omapzoom] BRIDGE Handle Node messaging when DSP crashed Ramirez Luna, Omar
2008-11-17 13:36 ` [FYI] Rebase: tidspbridge-20081118 Hiroshi DOYU
2008-11-19 21:37 ` Tony Lindgren
2008-11-20 8:21 ` Hiroshi DOYU
2008-11-20 17:29 ` 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=20081120172910.GJ4927@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.com \
--cc=x00omar@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