public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the rr tree
Date: Mon, 10 May 2010 22:03:53 +0930	[thread overview]
Message-ID: <201005102203.54784.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100510134620.2e06495b.sfr@canb.auug.org.au>

On Mon, 10 May 2010 01:16:20 pm Stephen Rothwell wrote:
> Hi Rusty,
> 
> On Mon, 10 May 2010 13:44:09 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > drivers/acpi/debug.c:141: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type
> > include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)'
> > 
> > Introduced by commit a1c3b92923eced4ee034fa15bf058f91e435e08c ("param:param_ops").
> 
> Also
> 
> drivers/message/fusion/mptbase.c:112: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type
> include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)'

Thanks, these are harmless, and I had followup patches outside linux-next
which resolve them.

I've now included them in the linux-next part of the series.

Thanks,
Rusty.

  reply	other threads:[~2010-05-10 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10  3:44 linux-next: build warnings after merge of the rr tree Stephen Rothwell
2010-05-10  3:46 ` Stephen Rothwell
2010-05-10 12:33   ` Rusty Russell [this message]
2010-05-10 15:53     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2011-12-28  2:58 Stephen Rothwell
2011-12-29  3:16 ` Rusty Russell
2011-12-29  6:52   ` 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=201005102203.54784.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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