From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] regmap: Fix build failure with CONFIG_DEBUG_FS=n
Date: Tue, 22 Nov 2011 10:28:36 +0100 [thread overview]
Message-ID: <20111122092836.GD19986@pengutronix.de> (raw)
In-Reply-To: <4ECB6992.5020804@pengutronix.de>
On Tue, Nov 22, 2011 at 10:21:22AM +0100, Marc Kleine-Budde wrote:
> On 11/22/2011 09:24 AM, Uwe Kleine-König wrote:
> > This fixes:
> >
> > drivers/base/regmap/regcache-rbtree.c: In function 'regcache_rbtree_init':
> > drivers/base/regmap/regcache-rbtree.c:197: error: 'struct regmap' has no member named 'debugfs'
> > drivers/base/regmap/regcache-rbtree.c:197: error: 'rbtree_fops' undeclared (first use in this function)
> > drivers/base/regmap/regcache-rbtree.c:197: error: (Each undeclared identifier is reported only once
> > drivers/base/regmap/regcache-rbtree.c:197: error: for each function it appears in.)
> >
> > which was introduced by commit
> >
> > bad2ab4 (regmap: Provide debugfs dump of the rbtree cache data)
> >
> > currently in next-20111122.
> >
> > Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > drivers/base/regmap/regcache-rbtree.c | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/base/regmap/regcache-rbtree.c b/drivers/base/regmap/regcache-rbtree.c
> > index 7767cbb..270ad65 100644
> > --- a/drivers/base/regmap/regcache-rbtree.c
> > +++ b/drivers/base/regmap/regcache-rbtree.c
> > @@ -194,7 +194,9 @@ static int regcache_rbtree_init(struct regmap *map)
> > goto err;
> > }
> >
> > +#ifdef CONFIG_DEBUG_FS
> > debugfs_create_file("rbtree", 0400, map->debugfs, map, &rbtree_fops);
> > +#endif
>
> What about introducing a debugfs_create_file() noop if debug-fs is not
> compiled in?
There is one, but that doesn't help map->debugfs or rbtree_fops being
available. Ah, unless the debugfs_create_file stub would be a macro but
currently it's a static inline.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-11-22 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 8:24 [PATCH] regmap: Fix build failure with CONFIG_DEBUG_FS=n Uwe Kleine-König
2011-11-22 9:21 ` Marc Kleine-Budde
2011-11-22 9:28 ` Uwe Kleine-König [this message]
2011-11-22 11:51 ` Mark Brown
2011-11-22 12:05 ` Marc Kleine-Budde
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=20111122092836.GD19986@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@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