From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Philip Rakity <prakity@marvell.com>
Cc: Liam Girdwood <lrg@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 1/2] regulator: Fix some bitrot in the machine driver documentation
Date: Thu, 6 Oct 2011 11:24:31 +0100 [thread overview]
Message-ID: <20111006102430.GD14518@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <94C474E6-A373-476B-935A-E675A5F57AED@marvell.com>
On Wed, Oct 05, 2011 at 06:39:56PM -0700, Philip Rakity wrote:
>
> Resend
>
> Did not make it yet into linux next.
Liam has been away for most of the past month unfortunately.
prev parent reply other threads:[~2011-10-06 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 17:41 [PATCH 1/2] regulator: Fix some bitrot in the machine driver documentation Mark Brown
2011-09-08 17:41 ` [PATCH 2/2] regulator: Clarify documentation for regulator-regulator supplies Mark Brown
2011-10-06 1:40 ` Philip Rakity
2011-10-06 1:39 ` [PATCH 1/2] regulator: Fix some bitrot in the machine driver documentation Philip Rakity
2011-10-06 10:24 ` Mark Brown [this message]
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=20111006102430.GD14518@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=prakity@marvell.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