From: David Miller <davem@davemloft.net>
To: brgl@bgdev.pl
Cc: grygorii.strashko@ti.com, nicolas.ferre@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
robh+dt@kernel.org, frowand.list@gmail.com, nsekhar@ti.com,
khilman@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-omap@vger.kernel.org,
bgolaszewski@baylibre.com
Subject: Re: [net-next][PATCH 0/4] davinci_emac: read the MAC address from nvmem
Date: Mon, 03 Dec 2018 15:40:59 -0800 (PST) [thread overview]
Message-ID: <20181203.154059.2288769104592341753.davem@davemloft.net> (raw)
In-Reply-To: <20181130082100.6241-1-brgl@bgdev.pl>
From: Bartosz Golaszewski <brgl@bgdev.pl>
Date: Fri, 30 Nov 2018 09:20:56 +0100
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> This series is part of a bigger series that aims at removing the platform
> data structure from the at24 EEPROM driver[1].
>
> We provide a generalized version of of_get_nvmem_mac_address(), switch the
> only user of the of_ variant to using it, remove the previous
> implementation and use the new routine in the davinci_emac driver.
>
> [1] https://lkml.org/lkml/2018/11/13/884
This looks good, series applied.
prev parent reply other threads:[~2018-12-03 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 8:20 [net-next][PATCH 0/4] davinci_emac: read the MAC address from nvmem Bartosz Golaszewski
2018-11-30 8:20 ` [net-next][PATCH 1/4] net: ethernet: provide nvmem_get_mac_address() Bartosz Golaszewski
2018-11-30 8:20 ` [net-next][PATCH 2/4] net: cadence: switch to using nvmem_get_mac_address() Bartosz Golaszewski
2018-11-30 8:20 ` [net-next][PATCH 3/4] of: net: kill of_get_nvmem_mac_address() Bartosz Golaszewski
2018-11-30 8:21 ` [net-next][PATCH 4/4] net: davinci_emac: use nvmem_get_mac_address() Bartosz Golaszewski
2018-12-03 23:40 ` 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=20181203.154059.2288769104592341753.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=hkallweit1@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@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 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).