From: David Miller <davem@davemloft.net>
To: shemming@brocade.com
Cc: vyasevic@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: remove dead code for add/del multiple
Date: Tue, 17 Dec 2013 15:14:27 -0500 (EST) [thread overview]
Message-ID: <20131217.151427.576275524292590944.davem@davemloft.net> (raw)
In-Reply-To: <20131213123556.4175da1b@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <shemming@brocade.com>
Date: Fri, 13 Dec 2013 12:35:56 -0800
> These function to manipulate multiple addresses are not used anywhere
> in current net-next tree. Some out of tree code maybe using these but
> too bad; they should submit their code upstream..
>
> Also, make __hw_addr_flush local since only used by dev_addr_lists.c
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Applied, thanks Stephen.
prev parent reply other threads:[~2013-12-17 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 20:35 [PATCH net-next] net: remove dead code for add/del multiple Stephen Hemminger
2013-12-14 2:27 ` Vladislav Yasevich
2013-12-17 20:14 ` 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=20131217.151427.576275524292590944.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemming@brocade.com \
--cc=vyasevic@redhat.com \
/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).