public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joel Stanley <joel@jms.id.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the aspeed tree
Date: Tue, 20 Aug 2024 09:34:24 +1000	[thread overview]
Message-ID: <20240820093424.24f9e652@canb.auug.org.au> (raw)

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

Hi all,

Commits

  995d8fe0341e ("ARM: dts: aspeed: System1: Updates to BMC board")
  76c553392543 ("ARM: dts: aspeed: convert ASRock SPC621D8HM3 NVMEM content to layout syntax")
  fdc26e0560a0 ("ARM: dts: aspeed: Add IBM P11 Fuji BMC system")
  787d4cbff0dc ("ARM: dts: aspeed: Add IBM P11 Blueridge 4U BMC system")
  fe1d09efd2ae ("ARM: dts: aspeed: Add IBM P11 Blueridge BMC system")
  e09e75d5c669 ("ARM: dts: aspeed: Add IBM P11 FSI devices")
  db769d76874e ("dt-bindings: arm: aspeed: add IBM P11 BMC boards")

are missing a Signed-off-by from their committer.

One of the catches with rebasing ...

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-08-19 23:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 23:34 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30  7:30 linux-next: Signed-off-by missing for commit in the aspeed tree Stephen Rothwell
2024-05-01  2:40 ` Joel Stanley
2023-03-10  2:06 Stephen Rothwell
2023-03-10  2:12 ` Joel Stanley
2022-11-03  5:37 Stephen Rothwell
2022-11-03  5:43 ` Joel Stanley
2021-07-18 22:03 Stephen Rothwell
2021-07-18 23:15 ` Joel Stanley

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=20240820093424.24f9e652@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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