From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: Fix regmap compilation with CONFIG_DEBUGFS=n
Date: Mon, 5 Sep 2011 12:55:37 -0700 [thread overview]
Message-ID: <20110905195536.GB11107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E6528CD.7080003@metafoo.de>
On Mon, Sep 05, 2011 at 09:53:49PM +0200, Lars-Peter Clausen wrote:
> On 09/05/2011 09:42 PM, Mark Brown wrote:
> > I sense that this doesn't actually happen in mainline...
> Uhm, yes... the patch is still valid though, want me to resubmit it with a
> different patch description?
Yes please, no problem with the patch itself but the description was
obviously bogus (it's fixing a future problem, not a current one).
prev parent reply other threads:[~2011-09-05 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 19:29 [PATCH] regmap: Fix regmap compilation with CONFIG_DEBUGFS=n Lars-Peter Clausen
2011-09-05 19:42 ` Mark Brown
2011-09-05 19:53 ` Lars-Peter Clausen
2011-09-05 19:55 ` 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=20110905195536.GB11107@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
/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