From: Sekhar Nori <nsekhar@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
GregKH <greg@kroah.com>, <maxime.ripard@free-electrons.com>,
<wsa@the-dreams.de>, <broonie@kernel.org>, <vz@mleia.com>,
<linux-kernel@vger.kernel.org>, <pantelis.antoniou@konsulko.com>,
<bgolaszewski@baylibre.com>, Kevin Hilman <khilman@kernel.org>
Subject: Re: [PATCHv6 7/7] misc: at24: replace memory_accessor with nvmem_device_read
Date: Fri, 26 Feb 2016 20:55:11 +0530 [thread overview]
Message-ID: <56D06E57.1000008@ti.com> (raw)
In-Reply-To: <20160223160847.GC25137@lunn.ch>
On Tuesday 23 February 2016 09:38 PM, Andrew Lunn wrote:
> Hi Sekhar
>
> Thanks for offering to test. You can get the series here:
>
> https://github.com/lunn/linux.git branch v4.5-rc3-nvmem
Tested on DM365 by verifying MAC address read continues to work
Tested-by: Sekhar Nori <nsekhar@ti.com>
Thanks,
Sekhar
next prev parent reply other threads:[~2016-02-26 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 23:17 [PATCHv6 0/7] Convert exiting EEPROM drivers to NVMEM Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 1/7] nvmem: Add flag to export NVMEM to root only Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 2/7] nvmem: Add backwards compatibility support for older EEPROM drivers Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 3/7] eeprom: at24: extend driver to plug into the NVMEM framework Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 4/7] eeprom: at25: Remove in kernel API for accessing the EEPROM Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 5/7] eeprom: at25: extend driver to plug into the NVMEM framework Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 6/7] eeprom: 93xx46: " Andrew Lunn
2016-02-18 23:17 ` [PATCHv6 7/7] misc: at24: replace memory_accessor with nvmem_device_read Andrew Lunn
2016-02-19 10:51 ` Srinivas Kandagatla
2016-02-23 15:55 ` Sekhar Nori
2016-02-23 16:08 ` Andrew Lunn
2016-02-26 15:25 ` Sekhar Nori [this message]
2016-02-26 17:33 ` Andrew Lunn
2016-02-26 18:55 ` Srinivas Kandagatla
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=56D06E57.1000008@ti.com \
--to=nsekhar@ti.com \
--cc=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vz@mleia.com \
--cc=wsa@the-dreams.de \
/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.