mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
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 08:00:17 +0200	[thread overview]
Message-ID: <e8688839-7686-47e9-a497-31b57abd46e2@amd.com> (raw)
In-Reply-To: <20240808083050.6ac578f9@canb.auug.org.au>

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

  reply	other threads:[~2024-08-08  6:00 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 [this message]
2024-08-08  7:18   ` Srinivas Kandagatla
2024-08-08 11:04     ` Michal Simek
  -- 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=e8688839-7686-47e9-a497-31b57abd46e2@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®