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:42:55 -0700 [thread overview]
Message-ID: <20110905194254.GA11107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1315250978-4242-1-git-send-email-lars@metafoo.de>
On Mon, Sep 05, 2011 at 09:29:38PM +0200, Lars-Peter Clausen wrote:
> With CONFIG_DEBUGFS disabled the regmap compilation fails with the following
> errors:
> drivers/base/regmap/regcache.o: In function `regmap_debugfs_initcall':
> drivers/base/regmap/internal.h:96: multiple definition of `regmap_debugfs_initcall'
> drivers/base/regmap/regmap.o:drivers/base/regmap/internal.h:96: first defined here
> drivers/base/regmap/regcache.o: In function `regmap_debugfs_init':
I sense that this doesn't actually happen in mainline...
next prev parent reply other threads:[~2011-09-05 19:43 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 [this message]
2011-09-05 19:53 ` Lars-Peter Clausen
2011-09-05 19:55 ` Mark Brown
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=20110905194254.GA11107@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