mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Boyd <bebarino@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] configs: Include MODULE_*() when CONFIG_IKCONFIG_PROC=n
Date: Tue, 21 Jun 2011 07:43:44 -0700	[thread overview]
Message-ID: <20110621074344.990cde5f.rdunlap@xenotime.net> (raw)
In-Reply-To: <1308636747-2360-1-git-send-email-bebarino@gmail.com>

On Mon, 20 Jun 2011 23:12:27 -0700 Stephen Boyd wrote:

> If CONFIG_IKCONFIG=m but CONFIG_IKCONFIG_PROC=n we get a module that has
> no MODULE_LICENSE definition. Move the MODULE_*() definitions outside
> the CONFIG_IKCONFIG_PROC #ifdef to prevent this configuration from
> tainting the kernel.
> 
> Signed-off-by: Stephen Boyd <bebarino@gmail.com>
> Cc: Randy Dunlap <rdunlap@xenotime.net>

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

Thanks.

> ---
>  kernel/configs.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/configs.c b/kernel/configs.c
> index b4066b4..42e8fa0 100644
> --- a/kernel/configs.c
> +++ b/kernel/configs.c
> @@ -92,8 +92,8 @@ static void __exit ikconfig_cleanup(void)
>  module_init(ikconfig_init);
>  module_exit(ikconfig_cleanup);
>  
> +#endif /* CONFIG_IKCONFIG_PROC */
> +
>  MODULE_LICENSE("GPL");
>  MODULE_AUTHOR("Randy Dunlap");
>  MODULE_DESCRIPTION("Echo the kernel .config file used to build the kernel");
> -
> -#endif /* CONFIG_IKCONFIG_PROC */
> -- 


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      parent reply	other threads:[~2011-06-21 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  6:12 Stephen Boyd
2011-06-21  6:41 ` Américo Wang
2011-06-21 14:43 ` Randy Dunlap [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=20110621074344.990cde5f.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=bebarino@gmail.com \
    --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

all inboxes | Powered by JetHome®