Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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
Thread-Topic: [PATCH v6 1/4] nvmem: core: add nvmem_device_find
Thread-Index: AQHVeU/izk9pg3Pj4EutFLPn+qErTQ==
Date:   Wed, 2 Oct 2019 18:33:28 +0000
Message-ID: <20191002183327.grhkxlbyu65vvhr4@pburton-laptop>
References: <20190923114636.6748-1-tbogendoerfer@suse.de>
 <20190923114636.6748-2-tbogendoerfer@suse.de>
 <ce44c762-f9a6-b4ef-fa8a-19ee4a6d391f@linaro.org>
In-Reply-To: <ce44c762-f9a6-b4ef-fa8a-19ee4a6d391f@linaro.org>
Accept-Language: en-US
Content-Language: en-US
user-agent: NeoMutt/20180716
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [12.94.197.246]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 26570fdc-ab56-4eab-f9cf-08d7476704a0
x-ms-traffictypediagnostic: MWHPR2201MB1728:
x-microsoft-antispam-prvs: <MWHPR2201MB1728A3B40E419150E36038B8C19C0@MWHPR2201MB1728.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-forefront-prvs: 0178184651
x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(7916004)(366004)(346002)(136003)(376002)(39850400004)(396003)(55674003)(51914003)(189003)(199004)(229853002)(99286004)(476003)(186003)(26005)(33716001)(446003)(486006)(7736002)(76176011)(44832011)(66556008)(6916009)(1076003)(66066001)(386003)(11346002)(7416002)(478600001)(102836004)(25786009)(52116002)(14454004)(5660300002)(4744005)(305945005)(6506007)(53546011)(3846002)(8676002)(316002)(4326008)(6246003)(6436002)(58126008)(42882007)(256004)(54906003)(2906002)(6116002)(71190400001)(71200400001)(66446008)(64756008)(66476007)(66946007)(81156014)(8936002)(81166006)(6486002)(9686003)(6512007);DIR:OUT;SFP:1102;SCL:1;SRVR:MWHPR2201MB1728;H:MWHPR2201MB1277.namprd22.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;MX:1;A:1;
received-spf: None (protection.outlook.com: wavecomp.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: OcLuc9kmZQnZ975cJcf7sfkyc7Ta3aSUnvXxqjJ/iiT0jVgnYFbgPs+Y7xr3mcvwb9szDk3fN/7ZaYYHY+6Zq1fvkYCak445zCrot+g2hwiFasPIDQC7PSePKu9roXokZhW7aMknMJID5mikX8Tdel+Z3EPsTY6zvgBiQHGgqQulmAe7Cb9RRkOTASyR+vLJHF7IygL8tx786GpLacegCTBqRmJQqS5uVVYKexIfjCGbAugt+DFrhhQA8l26dJskDu3rc7Bhda/njE37+8KnVH5q3hUJmNb9Kp2BEIXjdj6cwEvR1EIrpXF8Iq105sNkql+3V3qRa9bKdloF4Q0VL84VEE6V8UJTsaaGBEaOq1oafxUjHgfkXV36hcG33jiM9B+nTLdX9zLqg3exT/B/Qpe8zfTpI/Er1LGuGjdBqgs=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F75C05FC784E8D4589A7A23C018BBA8C@namprd22.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: mips.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 26570fdc-ab56-4eab-f9cf-08d7476704a0
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2019 18:33:28.4365
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 463607d3-1db3-40a0-8a29-970c56230104
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cxslBc7G3MeA2bVoNVt+BrLBaslT17n4DwWa8m+QkD4eqcfd912Dc8kYocR1/i9IVgx7RD3PnIaxEUpv0i/chw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR2201MB1728
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.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.
> >=20
> > Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> > ---
>=20
> Thanks for the patch,
> This patch looks good for me.
>=20
> Do you know which tree is going to pick this series up?
>=20
> I can either apply this patch to nvmem tree
>=20
> or here is my Ack for this patch to take it via other trees.
>=20
> 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