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 warning after merge of the rr tree
Date: Thu, 29 Dec 2011 13:50:06 +1030 [thread overview]
Message-ID: <87k45ggj2x.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111228181640.d299620c8e66237509fbba37@canb.auug.org.au>
On Wed, 28 Dec 2011 18:16:40 +1100, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
Non-text part: multipart/signed
> Hi Rusty,
>
> After merging the rr tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/net/virtio_net.c: In function 'virtnet_open':
> drivers/net/virtio_net.c:732:3: warning: passing argument 1 of 'queue_delayed_work' from incompatible pointer type [enabled by default]
> include/linux/workqueue.h:352:12: note: expected 'struct workqueue_struct *' but argument is of type 'struct workqueue_struct **'
Oops, thanks. Fixed.
Cheers,
Rusty.
next prev parent reply other threads:[~2011-12-29 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 7:16 linux-next: build warning after merge of the rr tree Stephen Rothwell
2011-12-29 3:20 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-18 3:41 Stephen Rothwell
2011-05-19 3:40 ` Rusty Russell
2010-06-03 1:48 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=87k45ggj2x.fsf@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