From: David Miller <davem@davemloft.net>
To: kaber@trash.net
Cc: netdev@vger.kernel.org
Subject: Re: [NET]: Fix multicast device ioctl checks
Date: Wed, 26 Mar 2008 02:12:47 -0700 (PDT) [thread overview]
Message-ID: <20080326.021247.33844390.davem@davemloft.net> (raw)
In-Reply-To: <47E8F61D.8040403@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Tue, 25 Mar 2008 13:54:53 +0100
> commit 33fb000e9d0b9b20c226383ce775f06fdcd426bc
> Author: Patrick McHardy <kaber@trash.net>
> Date: Tue Mar 25 13:53:52 2008 +0100
>
> [NET]: Fix multicast device ioctl checks
>
> SIOCADDMULTI/SIOCDELMULTI check whether the driver has a set_multicast_list
> method to determine whether it supports multicast. Drivers implementing
> secondary unicast support use set_rx_mode however.
>
> Check for both dev->set_multicast_mode and dev->set_rx_mode to determine
> multicast capabilities.
>
> Signed-off-by: Patrick McHardy <kaber@trash.net>
Applied and queued up for -stable, thanks!
prev parent reply other threads:[~2008-03-26 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 12:54 [NET]: Fix multicast device ioctl checks Patrick McHardy
2008-03-26 9:12 ` David Miller [this message]
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=20080326.021247.33844390.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.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).