From: Paul Burton <paul.burton@mips.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Thomas Bogendoerfer <tbogendoerfer@suse.de>,
Jonathan Corbet <corbet@lwn.net>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>, Lee Jones <lee.jones@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH v6 1/4] nvmem: core: add nvmem_device_find
Date: Wed, 2 Oct 2019 18:33:28 +0000 [thread overview]
Message-ID: <20191002183327.grhkxlbyu65vvhr4@pburton-laptop> (raw)
In-Reply-To: <ce44c762-f9a6-b4ef-fa8a-19ee4a6d391f@linaro.org>
Hello,
On Tue, Oct 01, 2019 at 11:11:58AM +0100, Srinivas Kandagatla wrote:
> On 23/09/2019 12:46, Thomas Bogendoerfer wrote:
> > nvmem_device_find provides a way to search for nvmem devices with
> > the help of a match function simlair to bus_find_device.
> >
> > Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> > ---
>
> Thanks for the patch,
> This patch looks good for me.
>
> Do you know which tree is going to pick this series up?
>
> I can either apply this patch to nvmem tree
>
> or here is my Ack for this patch to take it via other trees.
>
> Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Thanks - if you don't mind I'll take this through mips-next along with
the following patch that depends on it.
Thomas: I see patch 3 has an issue reported by the kbuild test robot,
and still needs acks from the MFD & network maintainers. Can I
presume it's safe to apply patches 1 & 2 without 3 & 4 in the
meantime?
Paul
next prev parent reply other threads:[~2019-10-02 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 11:46 [PATCH v6 0/4] Use MFD framework for SGI IOC3 drivers Thomas Bogendoerfer
2019-09-23 11:46 ` [PATCH v6 1/4] nvmem: core: add nvmem_device_find Thomas Bogendoerfer
2019-10-01 10:11 ` Srinivas Kandagatla
2019-10-02 18:33 ` Paul Burton [this message]
2019-10-02 19:08 ` Thomas Bogendoerfer
2019-09-23 11:46 ` [PATCH v6 2/4] MIPS: PCI: use information from 1-wire PROM for IOC3 detection Thomas Bogendoerfer
2019-09-23 11:46 ` [PATCH v6 3/4] mfd: ioc3: Add driver for SGI IOC3 chip Thomas Bogendoerfer
[not found] ` <201909232145.eyOJqt2k%lkp@intel.com>
2019-10-04 14:37 ` Lee Jones
2019-10-04 14:40 ` Lee Jones
2019-09-23 11:46 ` [PATCH v6 4/4] MIPS: SGI-IP27: fix readb/writeb addressing Thomas Bogendoerfer
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=20191002183327.grhkxlbyu65vvhr4@pburton-laptop \
--to=paul.burton@mips.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jhogan@kernel.org \
--cc=jslaby@suse.com \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tbogendoerfer@suse.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 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).