From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Pierre Ossman <pierre@ossman.eu>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-embedded@vger.kernel.org
Subject: Re: [PATCH 1/2] MMC Agressive clocking framework v3
Date: Sun, 21 Jun 2009 22:05:18 +0200 [thread overview]
Message-ID: <63386a3d0906211305yd09b4e6x488ac8b572af8204@mail.gmail.com> (raw)
In-Reply-To: <1245308220-25069-1-git-send-email-linus.walleij@stericsson.com>
2009/6/18 Linus Walleij <linus.walleij@stericsson.com>:
> diff --git a/drivers/mmc/core/Kconfig b/drivers/mmc/core/Kconfig
>(...)
> + Of unsure, say N.
However the rest of the patch is as I intended. I'll send a V4 pronto
if you want that for the current merge window.
Linus Walleij
next prev parent reply other threads:[~2009-06-21 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 6:57 [PATCH 1/2] MMC Agressive clocking framework v3 Linus Walleij
2009-06-21 20:05 ` Linus Walleij [this message]
2009-06-21 20:43 ` Pierre Ossman
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=63386a3d0906211305yd09b4e6x488ac8b572af8204@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-embedded@vger.kernel.org \
--cc=pierre@ossman.eu \
/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).