From: Chen Gang <gang.chen.5i5j@gmail.com>
To: gxt@mprc.pku.edu.cn
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [Consult] unicore32: Is unicore32 still alive?
Date: Mon, 17 Mar 2014 20:19:02 +0800 [thread overview]
Message-ID: <5326E836.7060407@gmail.com> (raw)
In-Reply-To: <5322592B.6060104@gmail.com>
Hello all:
As far as I know, unicore32 is still alive. If it will be obsoleted,
please let me know, so we can avoid the related spam about unicored32
(also can save my time resource).
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-03-17 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 1:19 [PATCH] arch/unicore32/kernel/clock.c: add readl() and writel() for 'PM_' macros Chen Gang
2014-03-17 12:19 ` Chen Gang [this message]
2014-03-17 12:47 ` 回复： [Consult] unicore32: Is unicore32 still alive? 管雪涛
2014-03-17 13:29 ` Chen Gang
2014-03-22 7:20 ` 回复： [PATCH] arch/unicore32/kernel/clock.c: add readl() and writel() for 'PM_' macros 管雪涛
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=5326E836.7060407@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
/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