From: "Girish" <girishsg@ti.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH 0/2] CPU id and silicon rev check support
Date: Fri, 26 Oct 2007 21:09:09 +0530 [thread overview]
Message-ID: <000101c817e6$59bb6770$6a8918ac@ent.ti.com> (raw)
Sorry, I guess the previous patch series might have got auto wrapped. Resending the patch series without auto wrapping.
Hi,
I am sending across patch series to support CPU identification and run-time silicon revision check for OMAP2/3.
Regards,
Girish
next reply other threads:[~2007-10-26 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 15:39 Girish [this message]
2007-10-26 16:03 ` [PATCH 0/2] CPU id and silicon rev check support Igor Stoppa
2007-10-26 17:20 ` Woodruff, Richard
-- strict thread matches above, loose matches on Subject: below --
2007-10-26 15:11 Girish
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='000101c817e6$59bb6770$6a8918ac@ent.ti.com' \
--to=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