All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the arm64 tree
Date: Tue, 29 Sep 2020 19:51:57 +1000	[thread overview]
Message-ID: <20200929195157.147ea306@canb.auug.org.au> (raw)

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

Hi all,

Commits

  9a313c5d65a5 ("arm64: Get rid of arm64_ssbd_state")
  d48ecc90a0e1 ("KVM: arm64: Convert ARCH_WORKAROUND_2 to arm64_get_spectre_v4_state()")
  780bb94b072e ("KVM: arm64: Get rid of kvm_arm_have_ssbd()")
  2197c8674ce3 ("KVM: arm64: Simplify handling of ARCH_WORKAROUND_2")
  977ce2df500e ("KVM: arm64: Set CSV2 for guests on hardware unaffected by Spectre-v2")

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

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-09-29  9:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  9:51 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-21 11:39 linux-next: Signed-off-by missing for commit in the arm64 tree Stephen Rothwell
2025-05-21 11:56 ` Rob Herring
2025-05-22 10:21   ` Will Deacon
2022-09-06 17:31 Stephen Rothwell
2022-09-06 22:01 ` Mark Brown
2022-07-20 13:12 Stephen Rothwell
2022-03-08 21:17 Stephen Rothwell
2021-03-23 21:14 Stephen Rothwell
2021-03-24 15:46 ` Catalin Marinas
2021-03-24 16:45   ` Andre Przywara
2017-11-07  5:31 Stephen Rothwell
2017-11-13 15:44 ` Will Deacon

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=20200929195157.147ea306@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.