From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: percpu net_device refcount
Date: Mon, 11 Oct 2010 21:51:25 +0200 [thread overview]
Message-ID: <1286826685.3218.16.camel@edumazet-laptop> (raw)
In-Reply-To: <20101011.124938.179933637.davem@davemloft.net>
Le lundi 11 octobre 2010 à 12:49 -0700, David Miller a écrit :
> Actually I have to revert, this breaks the infiniband drivers
> which access netdev->refcnt directly.
>
> drivers/infiniband/hw/nes/nes_verbs.c: In function 'nes_alloc_pd':
> drivers/infiniband/hw/nes/nes_verbs.c:786:2: error: 'struct net_device' has no member named 'refcnt'
> drivers/infiniband/hw/nes/nes_verbs.c: In function 'nes_create_qp':
> drivers/infiniband/hw/nes/nes_verbs.c:1418:2: error: 'struct net_device' has no member named 'refcnt'
> drivers/infiniband/hw/nes/nes_cm.c: In function 'nes_disconnect':
> drivers/infiniband/hw/nes/nes_cm.c:2703:2: error: 'struct net_device' has no member named 'refcnt'
> drivers/infiniband/hw/nes/nes_cm.c: In function 'nes_accept':
> drivers/infiniband/hw/nes/nes_cm.c:2793:2: error: 'struct net_device' has no member named 'refcnt'
Ah ok, I'll make a build test before submitting v3, sorry for the
inconvenience.
Thanks
next prev parent reply other threads:[~2010-10-11 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 17:12 [PATCH net-next] net: percpu net_device refcount Eric Dumazet
2010-10-07 17:30 ` Stephen Hemminger
2010-10-07 18:06 ` Eric Dumazet
2010-10-08 21:56 ` Paul E. McKenney
2010-10-09 6:23 ` Eric Dumazet
2010-10-09 16:58 ` Paul E. McKenney
2010-10-11 19:13 ` David Miller
2010-10-11 19:38 ` Eric Dumazet
2010-10-11 19:41 ` David Miller
2010-10-11 19:49 ` David Miller
2010-10-11 19:51 ` Eric Dumazet [this message]
2010-10-11 20:22 ` [PATCH net-next V3] " Eric Dumazet
2010-10-12 19:36 ` David Miller
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=1286826685.3218.16.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--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