mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: 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: linux-next: Fixes tag needs some work in the nvmem tree
Date: Mon, 30 Jan 2023 09:08:12 +1100	[thread overview]
Message-ID: <20230130090812.425adda2@canb.auug.org.au> (raw)

[-- 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 --]

             reply	other threads:[~2023-01-29 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 22:08 Stephen Rothwell [this message]
2024-01-22 20:28 Stephen Rothwell
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

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=20230130090812.425adda2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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®