From: Michal Simek <michal.simek@amd.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nvmem tree
Date: Thu, 8 Aug 2024 13:04:32 +0200 [thread overview]
Message-ID: <ee7817d6-8521-4855-9b21-17f04e628009@amd.com> (raw)
In-Reply-To: <aef4aad3-ea26-4ad9-ac86-f0906a0524c3@linaro.org>
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
next prev parent reply other threads:[~2024-08-08 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 22:30 Stephen Rothwell
2024-08-08 6:00 ` Michal Simek
2024-08-08 7:18 ` Srinivas Kandagatla
2024-08-08 11:04 ` Michal Simek [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 20:28 Stephen Rothwell
2023-01-29 22:08 Stephen Rothwell
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=ee7817d6-8521-4855-9b21-17f04e628009@amd.com \
--to=michal.simek@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=srinivas.kandagatla@linaro.org \
/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
all inboxes | Powered by JetHome®