Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <344a9a7f-a858-6d83-9cd8-ee97a2bd6a74@linaro.org>
Date:   Tue, 10 May 2022 10:29:04 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.7.0
Subject: Re: [PATCH 00/16] nvmem: patches (set 1) for 5.19
Content-Language: en-US
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org
References: <20220429162701.2222-1-srinivas.kandagatla@linaro.org>
 <YnkbcSiOYs0ZpjEP@kroah.com>
From:   Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
In-Reply-To: <YnkbcSiOYs0ZpjEP@kroah.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 09/05/2022 14:47, Greg KH wrote:
> On Fri, Apr 29, 2022 at 05:26:45PM +0100, Srinivas Kandagatla wrote:
>> Hi Greg,
>>
>> Here are some nvmem patches for 5.19 which includes
>>
>> - new nvmem provider for Apple efuses.
>> - support for regmap and TA 2.1 devices in sfp provider
>> - add device tree node support in nvmem cell info
>> - brcm_nvram provider to parse cells from dt.
>> - few minor clean ups in qfprom, bcm-ocotp and sunplus-ocotp
>>
>> Can you please queue them up for 5.19.
> 
> Not all of these applied cleanly.  Can you please rebase and resend the
> remaining ones?

Sure, looks like  there is only one patch("nvmem: brcm_nvram: check for 
allocation failure") that needs to be resent and I confirmed that all 
the other patches are already applied.

will resend that one.


--srini
> 
> thanks,
> 
> greg k-h