From: Wan ZongShun <mcuos.com@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Daniel Gl?ckner <dg@emlix.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] AsoC/s6000: use resource_size for {request/release}_mem_region and ioremap
Date: Wed, 2 Jun 2010 22:02:49 +0800 [thread overview]
Message-ID: <AANLkTikxdjFFF1HWLx2fu9sdJ9vsAzGP-uZta6TExdZl@mail.gmail.com> (raw)
In-Reply-To: <20100602135608.GA18071@sirena.org.uk>
2010/6/2 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> On Wed, Jun 02, 2010 at 09:40:13PM +0800, Wan ZongShun wrote:
>
>> Oh, it just be my worry.
>> If some codes were no longer useful or valuable, what should we do for them?
>> delete them or keep them be there yet?
>
>> If I my patch to fix a worthless codes, everything I do will be nothing.
>
> The hardware is still very much live, it's just that Daniel isn't
> working on it.
Of course, the s6000 is live, but we cannot indentify whether other
hardwares still live or not in all Linux tree.:)
>
--
*linux-arm-kernel mailing list
mail addr:linux-arm-kernel@lists.infradead.org
you can subscribe by:
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
* linux-arm-NUC900 mailing list
mail addr:NUC900@googlegroups.com
main web: https://groups.google.com/group/NUC900
you can subscribe it by sending me mail:
mcuos.com@gmail.com
next prev parent reply other threads:[~2010-06-02 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C063751.2060001@gmail.com>
2010-06-02 10:51 ` [PATCH] AsoC/s6000: use resource_size for {request/release}_mem_region and ioremap Mark Brown
2010-06-02 12:35 ` Daniel Glöckner
2010-06-02 12:45 ` Mark Brown
2010-06-02 13:35 ` [PATCH] MAINTAINERS: add entry for s6000 sound driver Daniel Glöckner
2010-06-02 14:45 ` Liam Girdwood
2010-06-02 14:46 ` Mark Brown
2010-06-02 13:40 ` [PATCH] AsoC/s6000: use resource_size for {request/release}_mem_region and ioremap Wan ZongShun
2010-06-02 13:56 ` Mark Brown
2010-06-02 14:02 ` Wan ZongShun [this message]
2010-06-02 13:03 ` Mark Brown
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=AANLkTikxdjFFF1HWLx2fu9sdJ9vsAzGP-uZta6TExdZl@mail.gmail.com \
--to=mcuos.com@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dg@emlix.com \
--cc=lrg@slimlogic.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).