From: tony@atomide.com
To: Kyungmin Park <kmpark@infradead.org>
Cc: 'Linux OMAP ML' <linux-omap-open-source@linux.omap.com>
Subject: Re: TSC2101/2102
Date: Tue, 20 Mar 2007 09:27:59 -0400 [thread overview]
Message-ID: <20070320132757.GB19913@atomide.com> (raw)
In-Reply-To: <006e01c76a91$8ee234e0$c7a3580a@swcenter.sec.samsung.co.kr>
Hi,
* Kyungmin Park <kmpark@infradead.org> [070319 21:47]:
>
> Umm the new updated git tree don't have tsc2301 commit. maybe it's missing :)
Just want to verify we haven't lost anything.. Are you talking about
commit a7b9b17c9025066cd05f555bbba5542bcf16df3a or something else?
At least a7b9b17c9025066cd05f555bbba5542bcf16df3a is there, if it's some
other commit you're talking about please let me know.
The commits in the master tree currently get buried easily as we have a
long series of patches in omap-upstream and omap-drivers and I keep rebasing
them continuously. This problem should disappear for most part once
omap-upstream is merged into Linus' tree.
Regards,
Tony
next prev parent reply other threads:[~2007-03-20 13:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 14:06 TSC2101/2102 Imre Deak
2007-03-09 14:23 ` TSC2101/2102 andrzej zaborowski
2007-03-14 13:21 ` TSC2101/2102 Nishanth Menon
2007-03-14 17:09 ` TSC2101/2102 Imre Deak
2007-03-14 20:35 ` TSC2101/2102 Dirk Behme
2007-03-15 1:18 ` TSC2101/2102 Kyungmin Park
2007-03-15 10:23 ` TSC2101/2102 Imre Deak
2007-03-15 14:23 ` Regarding use of DirectFB Raja Mallik
2007-03-15 17:09 ` Cliff Brake
2007-03-16 0:28 ` TSC2101/2102 Kyungmin Park
2007-03-16 7:41 ` TSC2101/2102 Imre Deak
2007-03-16 8:05 ` TSC2101/2102 Kyungmin Park
2007-03-16 9:49 ` TSC2101/2102 Imre Deak
2007-03-19 2:02 ` TSC2101/2102 Kyungmin Park
2007-03-19 7:37 ` TSC2101/2102 Jarkko Nikula
2007-03-19 8:04 ` TSC2101/2102 Kyungmin Park
2007-03-19 8:37 ` TSC2101/2102 Jarkko Nikula
2007-03-19 19:22 ` TSC2101/2102 tony
2007-03-20 1:46 ` TSC2101/2102 Kyungmin Park
2007-03-20 13:27 ` tony [this message]
2007-03-20 13:54 ` TSC2101/2102 Jarkko Nikula
2007-03-20 15:38 ` TSC2101/2102 Tony Lindgren
2007-03-21 19:24 ` TSC2101/2102 Eduardo Valentin
2007-03-22 6:48 ` TSC2101/2102 Jarkko Nikula
2007-03-30 18:49 ` TSC2101/2102 Tony Lindgren
2007-03-31 12:52 ` TSC2101/2102 Eduardo Valentin
2007-03-31 17:01 ` TSC2101/2102 Imre Deak
2007-04-02 13:43 ` TSC2101/2102 Eduardo Valentin
2007-04-02 20:23 ` TSC2101/2102 Imre Deak
2007-04-02 20:41 ` TSC2101/2102 Eduardo Valentin
2007-04-03 11:22 ` TSC2101/2102 Eduardo Valentin
2007-04-03 14:36 ` TSC2101/2102 Imre Deak
2007-04-03 15:10 ` TSC2101/2102 Eduardo Valentin
2007-04-03 19:23 ` TSC2101/2102 Tony Lindgren
2007-03-29 20:26 ` TSC2101/2102 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=20070320132757.GB19913@atomide.com \
--to=tony@atomide.com \
--cc=kmpark@infradead.org \
--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