From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org, davem@davemloft.net,
srn@prgmr.com
Subject: Re: [Bridge] [PATCH net-next] net: bridge: use rhashtable for fdbs
Date: Tue, 12 Dec 2017 10:02:24 -0800 [thread overview]
Message-ID: <20171212100224.1aa33a96@xeon-e3> (raw)
In-Reply-To: <1513087370-4791-1-git-send-email-nikolay@cumulusnetworks.com>
On Tue, 12 Dec 2017 16:02:50 +0200
Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
> + memcpy(__entry->addr, f->key.addr.addr, ETH_ALEN);
Maybe use ether_addr_copy() here?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
roopa@cumulusnetworks.com, srn@prgmr.com, davem@davemloft.net
Subject: Re: [PATCH net-next] net: bridge: use rhashtable for fdbs
Date: Tue, 12 Dec 2017 10:02:24 -0800 [thread overview]
Message-ID: <20171212100224.1aa33a96@xeon-e3> (raw)
In-Reply-To: <1513087370-4791-1-git-send-email-nikolay@cumulusnetworks.com>
On Tue, 12 Dec 2017 16:02:50 +0200
Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
> + memcpy(__entry->addr, f->key.addr.addr, ETH_ALEN);
Maybe use ether_addr_copy() here?
next prev parent reply other threads:[~2017-12-12 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:02 [Bridge] [PATCH net-next] net: bridge: use rhashtable for fdbs Nikolay Aleksandrov
2017-12-12 14:02 ` Nikolay Aleksandrov
2017-12-12 18:02 ` Stephen Hemminger [this message]
2017-12-12 18:02 ` Stephen Hemminger
2017-12-12 18:18 ` [Bridge] " Nikolay Aleksandrov
2017-12-12 18:18 ` Nikolay Aleksandrov
2017-12-12 18:07 ` [Bridge] " Stephen Hemminger
2017-12-12 18:07 ` Stephen Hemminger
2017-12-12 18:16 ` [Bridge] " Nikolay Aleksandrov
2017-12-12 18:16 ` Nikolay Aleksandrov
2017-12-13 20:10 ` [Bridge] " David Miller
2017-12-13 20:10 ` David Miller
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=20171212100224.1aa33a96@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=srn@prgmr.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 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.