From: Randy Dunlap <randy.dunlap@oracle.com>
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: wimax@linuxwimax.org, linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Toralf Förster" <toralf.foerster@gmx.de>,
"David Miller" <davem@davemloft.net>
Subject: Re: [PATCH] wimax: fix build issue when debugfs is disabled
Date: Thu, 29 Jan 2009 14:08:17 -0800 [thread overview]
Message-ID: <498228D1.7000105@oracle.com> (raw)
In-Reply-To: <1233266369-16834-1-git-send-email-inaky@linux.intel.com>
Inaky Perez-Gonzalez wrote:
> As reported by Toralf Förster and Randy Dunlap.
>
> - http://linuxwimax.org/pipermail/wimax/2009-January/000460.html
>
> - http://lkml.org/lkml/2009/1/29/279
Thanks. That one builds.
> The definitions needed for the wimax stack and i2400m driver debug
> infrastructure was, by mistake, compiled depending on CONFIG_DEBUG_FS
> (by them being placed in the debugfs.c files); thus the build broke in
> 2.6.29-rc3 when debugging was enabled (CONFIG_WIMAX_DEBUG) and
> DEBUG_FS was disabled.
>
> These definitions are always needed if debug is enabled at compile
> time (independently of DEBUG_FS being or not enabled), so moving them
> to a file that is always compiled fixes the issue.
>
> Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
> ---
> drivers/net/wimax/i2400m/debugfs.c | 14 --------------
> drivers/net/wimax/i2400m/driver.c | 16 ++++++++++++++++
> net/wimax/debugfs.c | 11 -----------
> net/wimax/stack.c | 13 +++++++++++++
> 4 files changed, 29 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/net/wimax/i2400m/debugfs.c b/drivers/net/wimax/i2400m/debugfs.c
> index 6266329..9b81af3 100644
> --- a/drivers/net/wimax/i2400m/debugfs.c
> +++ b/drivers/net/wimax/i2400m/debugfs.c
> @@ -234,20 +234,6 @@ struct dentry *debugfs_create_i2400m_reset(
> &fops_i2400m_reset);
> }
>
> -/*
> - * Debug levels control; see debug.h
> - */
> -struct d_level D_LEVEL[] = {
> - D_SUBMODULE_DEFINE(control),
> - D_SUBMODULE_DEFINE(driver),
> - D_SUBMODULE_DEFINE(debugfs),
> - D_SUBMODULE_DEFINE(fw),
> - D_SUBMODULE_DEFINE(netdev),
> - D_SUBMODULE_DEFINE(rfkill),
> - D_SUBMODULE_DEFINE(rx),
> - D_SUBMODULE_DEFINE(tx),
> -};
> -size_t D_LEVEL_SIZE = ARRAY_SIZE(D_LEVEL);
>
> #define __debugfs_register(prefix, name, parent) \
> do { \
> diff --git a/drivers/net/wimax/i2400m/driver.c b/drivers/net/wimax/i2400m/driver.c
> index 5f98047..e80a0b6 100644
> --- a/drivers/net/wimax/i2400m/driver.c
> +++ b/drivers/net/wimax/i2400m/driver.c
> @@ -707,6 +707,22 @@ void i2400m_release(struct i2400m *i2400m)
> EXPORT_SYMBOL_GPL(i2400m_release);
>
>
> +/*
> + * Debug levels control; see debug.h
> + */
> +struct d_level D_LEVEL[] = {
> + D_SUBMODULE_DEFINE(control),
> + D_SUBMODULE_DEFINE(driver),
> + D_SUBMODULE_DEFINE(debugfs),
> + D_SUBMODULE_DEFINE(fw),
> + D_SUBMODULE_DEFINE(netdev),
> + D_SUBMODULE_DEFINE(rfkill),
> + D_SUBMODULE_DEFINE(rx),
> + D_SUBMODULE_DEFINE(tx),
> +};
> +size_t D_LEVEL_SIZE = ARRAY_SIZE(D_LEVEL);
> +
> +
> static
> int __init i2400m_driver_init(void)
> {
> diff --git a/net/wimax/debugfs.c b/net/wimax/debugfs.c
> index 87cf443..94d216a 100644
> --- a/net/wimax/debugfs.c
> +++ b/net/wimax/debugfs.c
> @@ -28,17 +28,6 @@
> #include "debug-levels.h"
>
>
> -/* Debug framework control of debug levels */
> -struct d_level D_LEVEL[] = {
> - D_SUBMODULE_DEFINE(debugfs),
> - D_SUBMODULE_DEFINE(id_table),
> - D_SUBMODULE_DEFINE(op_msg),
> - D_SUBMODULE_DEFINE(op_reset),
> - D_SUBMODULE_DEFINE(op_rfkill),
> - D_SUBMODULE_DEFINE(stack),
> -};
> -size_t D_LEVEL_SIZE = ARRAY_SIZE(D_LEVEL);
> -
> #define __debugfs_register(prefix, name, parent) \
> do { \
> result = d_level_register_debugfs(prefix, name, parent); \
> diff --git a/net/wimax/stack.c b/net/wimax/stack.c
> index d4da92f..3869c03 100644
> --- a/net/wimax/stack.c
> +++ b/net/wimax/stack.c
> @@ -516,6 +516,19 @@ void wimax_dev_rm(struct wimax_dev *wimax_dev)
> }
> EXPORT_SYMBOL_GPL(wimax_dev_rm);
>
> +
> +/* Debug framework control of debug levels */
> +struct d_level D_LEVEL[] = {
> + D_SUBMODULE_DEFINE(debugfs),
> + D_SUBMODULE_DEFINE(id_table),
> + D_SUBMODULE_DEFINE(op_msg),
> + D_SUBMODULE_DEFINE(op_reset),
> + D_SUBMODULE_DEFINE(op_rfkill),
> + D_SUBMODULE_DEFINE(stack),
> +};
> +size_t D_LEVEL_SIZE = ARRAY_SIZE(D_LEVEL);
> +
> +
> struct genl_family wimax_gnl_family = {
> .id = GENL_ID_GENERATE,
> .name = "WiMAX",
--
~Randy
next prev parent reply other threads:[~2009-01-29 22:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901291030.n0TAUhRI003046@imap1.linux-foundation.org>
2009-01-29 17:33 ` [PATCH -next/mmotm/resend] kmemtrace: fix printk formats Randy Dunlap
2009-01-29 18:51 ` Ingo Molnar
2009-01-29 21:35 ` Geert Uytterhoeven
2009-01-29 21:49 ` Randy Dunlap
2009-01-30 7:46 ` Eduard - Gabriel Munteanu
2009-01-30 15:12 ` Ingo Molnar
2009-01-29 17:49 ` mmotm 2009-01-29-02-29 uploaded (wimax) Randy Dunlap
2009-01-29 18:58 ` Inaky Perez-Gonzalez
2009-01-29 19:23 ` Valdis.Kletnieks
2009-01-29 20:41 ` Randy Dunlap
2009-01-29 21:46 ` [GIT PATCH] " Inaky Perez-Gonzalez
2009-01-29 21:59 ` [PATCH] wimax: fix build issue when debugfs is disabled Inaky Perez-Gonzalez
2009-01-29 22:08 ` Randy Dunlap [this message]
2009-01-30 1:19 ` David Miller
2009-01-30 3:41 ` Inaky Perez-Gonzalez
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=498228D1.7000105@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--cc=wimax@linuxwimax.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