From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Patches sent upstream
Date: Fri, 15 Dec 2006 09:34:16 -0800 [thread overview]
Message-ID: <20061215173415.GA6478@atomide.com> (raw)
In-Reply-To: <4582C72D.9030402@gmail.com>
* Dirk Behme <dirk.behme@googlemail.com> [061215 08:03]:
> Tony Lindgren wrote:
> >I've sent a big pile of patches to RMK, which should pretty much bring
> >all the core omap code in sync with mainline except for DSP and STI.
>
> Did you get any answer from RMK? They are still in
> "Incoming" category of RMKs patch system.
I had forgotten to remove the OMAP_BOOT_TAG.. Russell notified me few
hours before the merge window closed and I made some last minute
changes to the patch series. But looks like it was too late for him,
or maybe he wants to take a closer look.
In any case, I'll keep that queue ready and keep the two trees in sync
so then there's just going to be tons more patches for next merge
attempt.
Regards,
Tony
prev parent reply other threads:[~2006-12-15 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 1:56 Patches sent upstream Tony Lindgren
2006-12-15 16:02 ` Dirk Behme
2006-12-15 17:34 ` 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=20061215173415.GA6478@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.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