From: David Miller <davem@davemloft.net>
To: bcrl@lhnet.ca
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] add HAVE_UNREGISTER_NETDEV_QUEUE define for out-of-tree modules
Date: Wed, 11 Nov 2009 11:24:57 -0800 (PST) [thread overview]
Message-ID: <20091111.112457.54237892.davem@davemloft.net> (raw)
In-Reply-To: <20091110220004.GT21704@kvack.org>
From: Benjamin LaHaise <bcrl@lhnet.ca>
Date: Tue, 10 Nov 2009 17:00:04 -0500
> I have an out of tree network driver (GPL'd) that would like to make use of
> the unregister_netdevice_queue interface for bulk unregister of devices.
> Add a #define HAVE_UNREGISTER_NETDEV_QUEUE to allow the source to detect
> that the kernel supports this.
Please get your code upstream :-)
We're already overcluttered with these "HAVE_PANTS", "HAVE_JACKET",
"HAVE_KITCHEN", "HAVE_SINK" ugly defines spewed all over netdevice.h,
and I'm not adding any more of that.
next prev parent reply other threads:[~2009-11-11 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 22:00 [PATCH] add HAVE_UNREGISTER_NETDEV_QUEUE define for out-of-tree modules Benjamin LaHaise
2009-11-11 19:24 ` David Miller [this message]
2009-11-11 19:49 ` Benjamin LaHaise
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=20091111.112457.54237892.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bcrl@lhnet.ca \
--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).