From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: derek.chickles@caviumnetworks.com,
satananda.burla@caviumnetworks.com,
felix.manlunas@caviumnetworks.com,
raghu.vatsavayi@caviumnetworks.com, ulli.kroll@googlemail.com,
linus.walleij@linaro.org, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, jeffrey.t.kirsher@intel.com,
bryan.whitehead@microchip.com, UNGLinuxDriver@microchip.com,
harish.patil@cavium.com, manish.chopra@cavium.com,
Dept-GELinuxNICDev@cavium.com, linux-net-drivers@solarflare.com,
ecree@solarflare.com, bkenward@solarflare.com,
grygorii.strashko@ti.com, w-kwok2@ti.com, m-karicheri2@ti.com,
jdmason@kudzu.us, dave.jiang@intel.com, allenbh@gmail.com,
woojung.huh@microchip.com, ath9k-devel@qca.qualcomm.com,
mareklindner@neomailbox.ch, sw@simonwunderlich.de, a@unstable.cc,
kvalo@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
intel-wired-lan@lists.osuosl.org, linux-omap@vger.kernel.org,
linux-ntb@googlegroups.com, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH] net: drivers/net: Convert random_ether_addr to eth_random_addr
Date: Sat, 23 Jun 2018 10:50:55 +0900 (KST) [thread overview]
Message-ID: <20180623.105055.470247977870986966.davem@davemloft.net> (raw)
In-Reply-To: <c558b59181756dfe647bcdeaf659c386701c0948.1529689773.git.joe@perches.com>
From: Joe Perches <joe@perches.com>
Date: Fri, 22 Jun 2018 10:51:00 -0700
> random_ether_addr is a #define for eth_random_addr which is
> generally preferred in kernel code by ~3:1
>
> Convert the uses of random_ether_addr to enable removing the #define
>
> Miscellanea:
>
> o Convert &vfmac[0] to equivalent vfmac and avoid unnecessary line wrap
>
> Signed-off-by: Joe Perches <joe@perches.com>
I'll apply this to net-next, thanks Joe.
prev parent reply other threads:[~2018-06-23 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 17:51 Joe Perches
2018-06-22 21:30 ` Jeff Kirsher
2018-06-23 1:50 ` 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=20180623.105055.470247977870986966.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Dept-GELinuxNICDev@cavium.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=a@unstable.cc \
--cc=allenbh@gmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bkenward@solarflare.com \
--cc=bryan.whitehead@microchip.com \
--cc=dave.jiang@intel.com \
--cc=derek.chickles@caviumnetworks.com \
--cc=ecree@solarflare.com \
--cc=felix.manlunas@caviumnetworks.com \
--cc=grygorii.strashko@ti.com \
--cc=harish.patil@cavium.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdmason@kudzu.us \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=kvalo@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-ntb@googlegroups.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=manish.chopra@cavium.com \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=raghu.vatsavayi@caviumnetworks.com \
--cc=salil.mehta@huawei.com \
--cc=satananda.burla@caviumnetworks.com \
--cc=sw@simonwunderlich.de \
--cc=ulli.kroll@googlemail.com \
--cc=w-kwok2@ti.com \
--cc=woojung.huh@microchip.com \
--cc=yisen.zhuang@huawei.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
all inboxes | Powered by JetHome®