From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batman-adv: Add dummy soft-interface rx mode handler
Date: Fri, 7 Jun 2013 23:16:44 +0200 [thread overview]
Message-ID: <20130607211644.GE6426@Linus-Debian> (raw)
In-Reply-To: <20130528155114.GA27671@Linus-Debian>
On Tue, May 28, 2013 at 05:51:14PM +0200, Linus Lüssing wrote:
> On Tue, May 28, 2013 at 05:55:44PM +0800, Marek Lindner wrote:
> > On Sunday, May 26, 2013 23:56:07 Linus Lüssing wrote:
> > > @@ -572,6 +584,7 @@ static const struct net_device_ops batadv_netdev_ops =
> > > { .ndo_get_stats = batadv_interface_stats,
> > > .ndo_set_mac_address = batadv_interface_set_mac_addr,
> > > .ndo_change_mtu = batadv_interface_change_mtu,
> > > + .ndo_set_rx_mode = batadv_interface_set_rx_mode,
> > > .ndo_start_xmit = batadv_interface_tx,
> > > .ndo_validate_addr = eth_validate_addr,
> > > .ndo_add_slave = batadv_softif_slave_add,
> >
> > Do we need compat code for this API call ?
> >
> > Cheers,
> > Marek
>
> Yes it does, actually. A PATCHv3 will follow soonish. Thanks for
> the hint!
Hm, I changed my mind, it actually shouldn't need any compat code.
At least compiling worked fine for me for 2.6.29 to 3.9 kernels.
There was a .ndo_set_multicast_list once with all these calls
being reassigned to .ndo_set_rx_mode and .ndo_set_multicast_list
being removed since 3.2 ("net: remove use of
ndo_set_multicast_list in drivers":afc4b13df143122f99a0eb10bfefb216c2806de0).
However .ndo_set_rx_mode has always been threre for
kernels >= 2.6.29, <= 3.9.
Cheers, Linus
next prev parent reply other threads:[~2013-06-07 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 15:56 [B.A.T.M.A.N.] [PATCHv2] batman-adv: Add dummy soft-interface rx mode handler Linus Lüssing
2013-05-28 9:55 ` Marek Lindner
2013-05-28 15:51 ` Linus Lüssing
2013-06-07 21:16 ` Linus Lüssing [this message]
2013-06-09 4:05 ` Marek Lindner
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=20130607211644.GE6426@Linus-Debian \
--to=linus.luessing@web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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