public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rakib Mullick <rakib.mullick@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Greg KH <greg@kroah•com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: tty tree build warning
Date: Thu, 21 Jan 2010 10:22:19 +0600	[thread overview]
Message-ID: <b9df5fa11001202022q22c2d81cs5b90f694be37c1f4@mail.gmail.com> (raw)
In-Reply-To: <20100120171901.b2e06465.sfr@canb.auug.org.au>

On 1/20/10, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Greg,
>
>  Today's linux-next build (x86_64 allmodconfig) produced this warning:
>
>  drivers/char/ip2/ip2main.c:511: warning: 'ip2_setup' defined but not used
>
Can we use module parameters? A check could be made if parameter hasn't
passed then we'll just return.

>  Introduced by commit 3f042287578018e0dc1c38b6f684767e657db62f ("ip2:
>  remove #ifdef MODULE from ip2main.c").
>
>  __setup() is a noop if CONFIG_MODULE is defined.
>
> --
>  Cheers,
>  Stephen Rothwell                    sfr@canb•auug.org.au
>  http://www.canb.auug.org.au/~sfr/
>
>

  reply	other threads:[~2010-01-21  4:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  6:19 linux-next: tty tree build warning Stephen Rothwell
2010-01-21  4:22 ` Rakib Mullick [this message]
2010-01-21 23:03   ` Greg KH
2010-01-23 12:53     ` Rakib Mullick
2010-01-23 14:43       ` Jiri Slaby
2010-01-24  3:42         ` Rakib Mullick
  -- strict thread matches above, loose matches on Subject: below --
2009-08-05  7:16 Stephen Rothwell
2009-08-05 13:29 ` Greg KH
2009-08-05 16:59   ` Greg KH
2009-08-06  0:12     ` Stephen Rothwell

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=b9df5fa11001202022q22c2d81cs5b90f694be37c1f4@mail.gmail.com \
    --to=rakib.mullick@gmail$(echo .)com \
    --cc=greg@kroah$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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