linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 08/18] net: davinci_emac: potentially get the MAC address from MTD
Date: Mon, 16 Jul 2018 14:10:05 +0200	[thread overview]
Message-ID: <20180716121005.GA23309@kroah.com> (raw)
In-Reply-To: <3b53a8a7-3f3a-4341-35b0-e7b52854fa9b@ti.com>

On Mon, Jul 16, 2018 at 05:27:00PM +0530, Sekhar Nori wrote:
> On Monday 16 July 2018 02:26 PM, Srinivas Kandagatla wrote:
> > 
> > 
> > On 16/07/18 09:50, Sekhar Nori wrote:
> >> On Friday 13 July 2018 11:30 PM, Bartosz Golaszewski wrote:
> >>
> >>> We're getting close to rc5 so I'd like to make a case for this series
> >>> again.
> >>>
> >>> I understand that there's more to do than just the changes introduced
> >>> here, but we shouldn't try to fix several problems in many different
> >>> places at once. There's just too many moving pieces. I'd rather start
> >>> merging small improvements right away.
> >>>
> >>> The idea behind this series is to remove (almost) all users of
> >>> at24_platform_data. The davinci_emac patches are there only because we
> >>> need to remove some MAC adress reading stuff from the board files.
> >>> Having this code there and calling it back from EEPROM/MTD drivers is
> >>> already wrong and we should work towards using nvmem for that anyway.
> >>>
> >>> Currently for MTD the nvmem support series seems to be dead and it's
> >>> going to take some time before anything gets upstream.
> >>>
> >>> So I'd like to again ask you to consider picking up the patches from
> >>> this series to your respective trees or at the very least: I'd like to
> >>> ask Srinivas to pick up the nvmem patches and Sekhar to take the
> >>> first, non-controversial batch of davinci platform changes so that
> >>> we'll have less code to carry for the next release.
> >>
> >> I think those are patches 3-7. I can take those if I get an immutable
> >> commit over v4.18-rc1 from Srinivas with patches 1 & 2 applied.
> 
> > nvmem patches go via Greg KH char-misc tree, if it makes things easy I
> > can provide Ack on nvmem patches, so that you can take these patches via
> > your tree?
> > 
> > Let me know.
> 
> I can do that.
> 
> Greg, are you fine with this? It will be great to have your ack for
> patches 1/8 and 2/18.

I'm not the nvmem maintainer :)

  reply	other threads:[~2018-07-16 12:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  9:40 [PATCH v4 00/18] ARM: davinci: step towards removing at24_platform_data Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 01/18] nvmem: add support for cell lookups Bartosz Golaszewski
2018-07-16 12:19   ` Srinivas Kandagatla
2018-07-16 12:20   ` Srinivas Kandagatla
2018-06-29  9:40 ` [PATCH v4 02/18] Documentation: nvmem: document lookup entries Bartosz Golaszewski
2018-07-16 12:14   ` Sekhar Nori
2018-07-16 12:18   ` Srinivas Kandagatla
2018-06-29  9:40 ` [PATCH v4 03/18] ARM: davinci: dm365-evm: use nvmem lookup for mac address Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 04/18] ARM: davinci: dm644-evm: " Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 05/18] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 06/18] ARM: davinci: da830-evm: " Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 07/18] ARM: davinci: mityomapl138: add nvmem cells lookup entries Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 08/18] net: davinci_emac: potentially get the MAC address from MTD Bartosz Golaszewski
2018-06-29 20:09   ` David Lechner
2018-06-29 20:35     ` David Lechner
2018-07-02  7:41       ` Bartosz Golaszewski
2018-07-03 16:39   ` Florian Fainelli
2018-07-03 16:47     ` David Lechner
2018-07-04  7:09     ` Ladislav Michl
2018-07-04  8:29       ` Bartosz Golaszewski
2018-07-04  9:04         ` Sekhar Nori
2018-07-13 18:00           ` Bartosz Golaszewski
2018-07-16  8:50             ` Sekhar Nori
2018-07-16  8:56               ` Srinivas Kandagatla
2018-07-16 11:57                 ` Sekhar Nori
2018-07-16 12:10                   ` Greg Kroah-Hartman [this message]
2018-07-16 12:13                     ` Sekhar Nori
2018-07-20  5:04                 ` Sekhar Nori
2018-07-27  9:52                   ` Sekhar Nori
2018-06-29  9:40 ` [PATCH v4 09/18] ARM: davinci: da850-evm: remove dead MTD code Bartosz Golaszewski
2018-06-29 17:09   ` David Lechner
2018-07-02  7:28     ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 10/18] net: davinci_emac: use nvmem to retrieve the mac address Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 11/18] ARM: davinci: mityomapl138: don't read the MAC address from machine code Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 12/18] ARM: davinci: dm365-evm: use device properties for at24 eeprom Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 13/18] ARM: davinci: da830-evm: " Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 14/18] ARM: davinci: dm644x-evm: " Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 15/18] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 16/18] ARM: davinci: sffsdr: fix the at24 eeprom device name Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 17/18] ARM: davinci: sffsdr: use device properties for at24 eeprom Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 18/18] ARM: davinci: remove dead code related to MAC address reading Bartosz Golaszewski

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=20180716121005.GA23309@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.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).