From: David Miller <davem@davemloft.net>
To: kennylewis@gmail.com
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [build fail] rt2x00dev.c from next tree causes build fail
Date: Sat, 12 Sep 2009 00:46:50 -0700 (PDT) [thread overview]
Message-ID: <20090912.004650.21685836.davem@davemloft.net> (raw)
In-Reply-To: <5a44caba0909120042x6592e261icca4b21c4184e0d3@mail.gmail.com>
From: Ken Lewis <kennylewis@gmail.com>
Date: Sat, 12 Sep 2009 08:42:17 +0100
> I've been getting build failures in the next tree since next-20090903,
> also experienced up to next-20090910, which I've not been able to
> investigate, due to a lack of time and git-fu. rt2x00dev.c causes the
> following:
Please use netdev not linux-net, for development discussion
>
> LD drivers/net/wireless/rt2x00/built-in.o
> CC [M] drivers/net/wireless/rt2x00/rt2x00dev.o
> drivers/net/wireless/rt2x00/rt2x00dev.c: In function ‘rt2x00lib_rxdone’:
> drivers/net/wireless/rt2x00/rt2x00dev.c:405: warning: passing argument
> 3 of ‘rt2x00crypto_rx_insert_iv’ makes integer from pointer without a
> cast
> drivers/net/wireless/rt2x00/rt2x00lib.h:383: note: expected ‘unsigned
> int’ but argument is of type ‘struct rxdone_entry_desc *’
> drivers/net/wireless/rt2x00/rt2x00dev.c:405: error: too few arguments
> to function ‘rt2x00crypto_rx_insert_iv’
> make[4]: *** [drivers/net/wireless/rt2x00/rt2x00dev.o] Error 1
> make[3]: *** [drivers/net/wireless/rt2x00] Error 2
> make[2]: *** [drivers/net/wireless] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> I've attached my .config if relevant.
I wonder if this was created by the crypto merge.
parent reply other threads:[~2009-09-12 7:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5a44caba0909120042x6592e261icca4b21c4184e0d3@mail.gmail.com>]
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=20090912.004650.21685836.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kennylewis@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).