From: Phil Sutter <phil@nwl.cc>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] Minor IFF_NO_QUEUE conversion follow-up
Date: Fri, 15 Apr 2016 19:14:18 +0200 [thread overview]
Message-ID: <1460740460-12859-1-git-send-email-phil@nwl.cc> (raw)
The following series converts two further drivers away from setting
'tx_queue_len = 0' to adding IFF_NO_QUEUE to priv_flags instead.
The first one, rtl8188eu in staging didn't exist back when all drivers
were converted. The second one, openvswitch seems to have slipped through
my grep'ing back then, no idea why.
Phil Sutter (2):
staging: rtl8188eu: Convert to using IFF_NO_QUEUE
openvswitch: Convert to using IFF_NO_QUEUE
drivers/staging/rtl8188eu/os_dep/mon.c | 2 +-
net/openvswitch/vport-internal_dev.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.8.0
next reply other threads:[~2016-04-15 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 17:14 Phil Sutter [this message]
2016-04-15 17:14 ` [PATCH net-next 1/2] staging: rtl8188eu: Convert to using IFF_NO_QUEUE Phil Sutter
2016-04-15 17:14 ` [PATCH net-next 2/2] openvswitch: " Phil Sutter
2016-04-17 2:02 ` [PATCH net-next 0/2] Minor IFF_NO_QUEUE conversion follow-up 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=1460740460-12859-1-git-send-email-phil@nwl.cc \
--to=phil@nwl.cc \
--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;
as well as URLs for NNTP newsgroup(s).