From: David Ahern <dsa@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 2/5] net: Add netif_is_l3_slave
Date: Mon, 5 Oct 2015 08:44:31 -0600 [thread overview]
Message-ID: <56128CCF.3080209@cumulusnetworks.com> (raw)
In-Reply-To: <1443713247-11230-3-git-send-email-dsa@cumulusnetworks.com>
On 10/1/15 9:27 AM, David Ahern wrote:
> IPv6 addrconf keys off of IFF_SLAVE so can not use it for L3 slave.
> Add a new private flag and add netif_is_l3_slave function for checking
> it.
After pulling in Cong's patch to address the warning on device remove I
need to respin this one.
next prev parent reply other threads:[~2015-10-05 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 15:27 [PATCH net-next 0/5] net: Add saddr op to l3mdev and vrf David Ahern
2015-10-01 15:27 ` [PATCH net-next 1/5] net: Rename FLOWI_FLAG_VRFSRC to FLOWI_FLAG_L3MDEV_SRC David Ahern
2015-10-01 15:27 ` [PATCH net-next 2/5] net: Add netif_is_l3_slave David Ahern
2015-10-05 14:44 ` David Ahern [this message]
2015-10-01 15:27 ` [PATCH net-next 3/5] net: Refactor path selection in __ip_route_output_key David Ahern
2015-10-02 6:20 ` kbuild test robot
2015-10-02 16:04 ` Fwd: " David Ahern
2015-10-05 10:11 ` Joshua Kinard
2015-10-05 13:38 ` David Miller
2015-10-05 14:08 ` David Ahern
2015-10-01 15:27 ` [PATCH net-next 4/5] net: Add source address lookup op for VRF David Ahern
2015-10-01 15:27 ` [PATCH net-next 5/5] net: Add l3mdev saddr lookup to raw_sendmsg David Ahern
-- strict thread matches above, loose matches on Subject: below --
2015-10-05 15:51 [PATCH net-next 0/5 v2] net: Add saddr op to l3mdev and vrf David Ahern
2015-10-05 15:51 ` [PATCH net-next 2/5] net: Add netif_is_l3_slave David Ahern
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=56128CCF.3080209@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.