From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 12/15] MMC: au1xmmc: remove Alchemy CPU subtype dependencies
Date: Wed, 3 Aug 2011 13:06:27 +0100 [thread overview]
Message-ID: <20110803120627.GA856@linux-mips.org> (raw)
In-Reply-To: <1312307470-6841-13-git-send-email-manuel.lauss@googlemail.com>
On Tue, Aug 02, 2011 at 07:51:07PM +0200, Manuel Lauss wrote:
> Replace all occurrences of CONFIG_SOC_AU1??? with runtime feature
> detection.
>
> Cc: <linux-mmc@vger.kernel.org>
> Signed-off-by: Manuel Lauss <manuel.lauss@googlemail.com>
> ---
> I'd like for this patch to go in via the mips tree since a few more depend
> on it.
Patch is looking ok. Since MMC is orphaned I've just queued it and it
will go to linux-next after -rc1.
Ralf
next prev parent reply other threads:[~2011-08-03 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1312307470-6841-1-git-send-email-manuel.lauss@googlemail.com>
2011-08-02 17:51 ` [PATCH 12/15] MMC: au1xmmc: remove Alchemy CPU subtype dependencies Manuel Lauss
2011-08-03 12:06 ` Ralf Baechle [this message]
2011-08-03 18:40 ` Chris Ball
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=20110803120627.GA856@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=manuel.lauss@googlemail.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