From: Tony Lindgren <tony@atomide.com>
To: Girish <girishsg@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 1/3] CPU identification support for 3430
Date: Wed, 14 Nov 2007 18:14:16 -0800 [thread overview]
Message-ID: <20071115021416.GH6005@atomide.com> (raw)
In-Reply-To: <00f101c81d5e$be25aa90$6a8918ac@ent.ti.com>
* Girish <girishsg@ti.com> [071102 07:44]:
> This patch add cpu identification support for 3430 and some code clean up.
Pushing today.
Tony
prev parent reply other threads:[~2007-11-15 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 14:43 [PATCH 1/3] CPU identification support for 3430 Girish
2007-11-15 2:14 ` 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=20071115021416.GH6005@atomide.com \
--to=tony@atomide.com \
--cc=girishsg@ti.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