From: Patrick McHardy <kaber@trash.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org
Subject: Re: set_multicast_list vs. set_rx_mode
Date: Wed, 15 Aug 2007 14:33:57 +0200 [thread overview]
Message-ID: <46C2F2B5.60803@trash.net> (raw)
In-Reply-To: <1187181208.3998.44.camel@johannes.berg>
Johannes Berg wrote:
> Is it intentional that in the case where set_rx_mode is assigned, you
> still need to assign set_multicast_list even if it won't ever be called
> as a flag for SIOCADDMULTI?
>
> I was thinking of converting the wireless code to use set_rx_mode and
> assign set_multicast_list only if the underlying hardware supports
> multicast filtering, and it seems that is well-supported, but it does
> seem a bit weird that set_multicast_list degrades to a flag.
Indeed, I missed that. It should check for !dev->set_multicast_list &&
!dev->set_rx_mode before returning -EINVAL.
next prev parent reply other threads:[~2007-08-15 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 12:33 set_multicast_list vs. set_rx_mode Johannes Berg
2007-08-15 12:33 ` Patrick McHardy [this message]
2007-08-15 12:44 ` Johannes Berg
2007-08-15 12:55 ` Johannes Berg
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=46C2F2B5.60803@trash.net \
--to=kaber@trash.net \
--cc=johannes@sipsolutions.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