From: David Miller <davem@davemloft.net>
To: lkundrak@v3.sk
Cc: sathya.perla@broadcom.com, ajit.khaparde@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] benet: remove broken and unused macro
Date: Mon, 28 Jan 2019 10:56:25 -0800 (PST) [thread overview]
Message-ID: <20190128.105625.1531145408099541707.davem@davemloft.net> (raw)
In-Reply-To: <20190128161740.16129-1-lkundrak@v3.sk>
From: Lubomir Rintel <lkundrak@v3.sk>
Date: Mon, 28 Jan 2019 17:17:40 +0100
> is_broadcast_packet() expands to compare_ether_addr() which doesn't
> exist since commit 7367d0b573d1 ("drivers/net: Convert uses of
> compare_ether_addr to ether_addr_equal"). It turns out it's actually not
> used.
>
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
Applied to net-next.
prev parent reply other threads:[~2019-01-28 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 16:17 [PATCH] benet: remove broken and unused macro Lubomir Rintel
2019-01-28 18:56 ` 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=20190128.105625.1531145408099541707.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajit.khaparde@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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).