From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-next@vger.kernel.org,
Ben Hutchings <bhutchings@solarflare.com>,
Ilya Yanok <yanok@emcraft.com>
Subject: linux-next: net-current/net tree build failure
Date: Fri, 13 Mar 2009 13:16:55 +1100 [thread overview]
Message-ID: <20090313131655.33117fb9.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi Dave,
Today's linux-next build (x86_64 allmodconfig) failed like this:
drivers/net/dnet.c: In function 'dnet_poll':
drivers/net/dnet.c:411: error: implicit declaration of function 'netif_rx_complete'
drivers/net/dnet.c: In function 'dnet_interrupt':
drivers/net/dnet.c:510: error: implicit declaration of function 'netif_rx_schedule_prep'
drivers/net/dnet.c:519: error: implicit declaration of function '__netif_rx_schedule'
Caused by commit 4796417417a62e2ae83d92cb92e1ecf9ec67b5f5 ("dnet: Dave
DNET ethernet controller driver (updated)") from the net-current tree
interacting with commit 288379f050284087578b77e04f040b57db3db3f8 ("net:
Remove redundant NAPI functions") from the net tree.
So for today, I have reverted the net-current commit and commit
2c5849ea38fdad477d72dcf1c8c4842db4b33aae ("dnet: Fix warnings on 64-bit")
that depended on it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-03-13 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 2:16 Stephen Rothwell [this message]
2009-03-13 10:30 ` [PATCH] dnet: replace obsolete *netif_rx_* functions with *napi_* Ilya Yanok
2009-03-13 16:51 ` David Miller
2009-03-13 17:23 ` linux-next: net-current/net tree build failure David Miller
2009-03-15 11:30 ` 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=20090313131655.33117fb9.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=yanok@emcraft.com \
/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