Message-ID: <ef5e4ea6-6dcb-3700-a8e5-2b7ec5aad092@linaro.org>
Date:   Mon, 30 Jan 2023 11:03:03 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: [PATCH 00/10] nvmem: fixes for 6.2
Content-Language: en-US
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org
References: <20230127104015.23839-1-srinivas.kandagatla@linaro.org>
 <Y9Ulm3So08Fg308w@kroah.com>
From:   Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
In-Reply-To: <Y9Ulm3So08Fg308w@kroah.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Thanks Greg,

On 28/01/2023 13:39, Greg KH wrote:
> On Fri, Jan 27, 2023 at 10:40:05AM +0000, Srinivas Kandagatla wrote:
>> Hi Greg,
>>
>> Here are some nvmem core fixes around nvmem provider device register
>> and error paths.
>> Most of these patches have been in next for 2-3 weeks.
>>
>> Am really not sure if you are taking fixes late in this cycle.
>> In case you are not could you please apply them for 6.3
> 
> When I apply them, I get the following errors from the scripts:
> 
> Commit: 36f5dbea16ad ("nvmem: core: fix return value")
> 	Fixes tag: Fixes: 60c8b4aebd8e ("nvmem: core: fix cleanup after dev_set_name()")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: 7de8892c0527 ("nvmem: core: fix device node refcounting")
> 	Fixes tag: Fixes: 69aba7948cbe("nvmem: Add a simple NVMEM framework for consumers")
> 	Has these problem(s):
> 		- missing space between the SHA1 and the subject
> 
> The first one is because you have your own git tree, that's fine.  But the
> second one should have given you an error when it was in linux-next, what
> happened?
> 
> Let me see if I can fix this up...

Thankyou very much for fixing this up before applying, will take extra 
care next time. :-)

thanks,
srini
> 
> greg k-h