From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@freescale.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH] backlight: Fix broken regulator API usage in l4f00242t03
Date: Mon, 5 Sep 2011 22:45:38 -0700 [thread overview]
Message-ID: <20110906054537.GB20379@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E659A56.9060305@gmx.de>
On Tue, Sep 06, 2011 at 03:58:14AM +0000, Florian Tobias Schandinat wrote:
> Hm, it looks like Richard did not respond on this email address for months. But
> I noticed there exists a Richard@linuxfoundation and according to
> http://lwn.net/Articles/419640/rss
> I'd guess it is the same person. If this is true, would you, Richard, *please*
> update your email address in MAINTAINERS so people do not needlessly wait for
> feedback for ages.
> For the patch itself, it looks good to me, but I really feel not qualified to
> handle the backlight things. So I'll let handle Andrew any backlight patches for
> now but could carry patches in my tree if they get Richard's Ack/Signed-off.
They're both the same Richard and as far as I know both addresses work
just as well, it's not an e-mail issue but more that Richard has been
focusing on things other than kernel work recently and Andrew has been
picking things up instead (as can be seen in the git history).
prev parent reply other threads:[~2011-09-06 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 18:10 [PATCH] backlight: Fix broken regulator API usage in l4f00242t03 Mark Brown
2011-09-06 3:58 ` Florian Tobias Schandinat
2011-09-06 5:45 ` 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=20110906054537.GB20379@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=FlorianSchandinat@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=fabio.estevam@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rpurdie@rpsys.net \
--cc=s.hauer@pengutronix.de \
/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