linux-next: Fixes tag needs some work in the nvmem tree

linux-next: Fixes tag needs some work in the nvmem tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 354 bytes --]

Hi all,

In commit

  b40fed138700 ("nvmem: include bit index in cell sysfs file name")

Fixes tag

  Fixes: 0088cbc19276 ("nvmem: core: Expose cells through sysfs")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 0331c611949f ("nvmem: core: Expose cells through sysfs")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: Fixes tag needs some work in the nvmem tree

[Michal Simek]

On 8/8/24 09:18, Srinivas Kandagatla wrote:
> 
> 
> On 08/08/2024 07:00, Michal Simek wrote:
>> Hi Stephen,
>>
>> On 8/8/24 00:30, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> In commit
>>>
>>>    c258adca4fb4 ("dt-bindings: nvmem: Use soc-nvmem node name instead of nvmem")
>>>
>>> Fixes tag
>>>
>>>    Fixes: a0cfd5e99782 ("dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to 
>>> yaml")
>>>
>>> has these problem(s):
>>>
>>>    - Target SHA1 does not exist
>>>
>>> Maybe you meant
>>>
>>> Fixes: c7f99cd8fb6b ("dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to 
>>> yaml")
>>
>> thanks for reporting. You are right and I have no idea where a0cfd5e99782 is 
>> coming from because I even don't have this sha1 in my tree.
>>
>> Anyway that's my patch and issue on my side and I am sorry for it.
>>
>> Srinivas: What do you want me to do? Send updated one or are you able to 
>> update the patch itself? Please let me know what you want me to do.
> 
> Please send me a new version with fix.

here it is.

https://lore.kernel.org/all/1184b2799ecdeef04128f4bab3db7460fd8edb10.1723114978.git.michal.simek@amd.com/

Thanks,
Michal

Re: linux-next: Fixes tag needs some work in the nvmem tree

[Srinivas Kandagatla]

On 08/08/2024 07:00, Michal Simek wrote:
> Hi Stephen,
> 
> On 8/8/24 00:30, Stephen Rothwell wrote:
>> Hi all,
>>
>> In commit
>>
>>    c258adca4fb4 ("dt-bindings: nvmem: Use soc-nvmem node name instead 
>> of nvmem")
>>
>> Fixes tag
>>
>>    Fixes: a0cfd5e99782 ("dt-bindings: nvmem: Convert 
>> xlnx,zynqmp-nvmem.txt to yaml")
>>
>> has these problem(s):
>>
>>    - Target SHA1 does not exist
>>
>> Maybe you meant
>>
>> Fixes: c7f99cd8fb6b ("dt-bindings: nvmem: Convert 
>> xlnx,zynqmp-nvmem.txt to yaml")
> 
> thanks for reporting. You are right and I have no idea where 
> a0cfd5e99782 is coming from because I even don't have this sha1 in my tree.
> 
> Anyway that's my patch and issue on my side and I am sorry for it.
> 
> Srinivas: What do you want me to do? Send updated one or are you able to 
> update the patch itself? Please let me know what you want me to do.

Please send me a new version with fix.

--srini
> 
> Thanks,
> Michal

Re: linux-next: Fixes tag needs some work in the nvmem tree

[Michal Simek]

Hi Stephen,

On 8/8/24 00:30, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    c258adca4fb4 ("dt-bindings: nvmem: Use soc-nvmem node name instead of nvmem")
> 
> Fixes tag
> 
>    Fixes: a0cfd5e99782 ("dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml")
> 
> has these problem(s):
> 
>    - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: c7f99cd8fb6b ("dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml")

thanks for reporting. You are right and I have no idea where a0cfd5e99782 is 
coming from because I even don't have this sha1 in my tree.

Anyway that's my patch and issue on my side and I am sorry for it.

Srinivas: What do you want me to do? Send updated one or are you able to update 
the patch itself? Please let me know what you want me to do.

Thanks,
Michal

linux-next: Fixes tag needs some work in the nvmem tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 402 bytes --]

Hi all,

In commit

  c258adca4fb4 ("dt-bindings: nvmem: Use soc-nvmem node name instead of nvmem")

Fixes tag

  Fixes: a0cfd5e99782 ("dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: c7f99cd8fb6b ("dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

linux-next: Fixes tag needs some work in the nvmem tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

Hi all,

In commit

  ee0a7b467d3a ("nvmem: stm32: fix OPTEE dependency")

Fixes tag

  Fixes: ae46fd89cc0cc ("nvmem: stm32: add OP-TEE support for STM32MP13x")

has these problem(s):

  - Target SHA1 does not exist

In commit

  32de71ca36e2 ("of: property: fix #nvmem-cell-cells parsing")

Fixes tag

  Fixes: 6a80b3e6fb41 ("of: property: make #.*-cells optional for simple props")

has these problem(s):

  - Target SHA1 does not exist

In commit

  059e01d5b3a6 ("nvmem: core: fix nvmem_layout_get_match_data()")

Fixes tag

  Fixes: f61a093b4a0e ("nvmem: core: introduce NVMEM layouts")

has these problem(s):

  - Target SHA1 does not exist

In commit

  c976fd0b6970 ("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

Rebased?

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]