Linux-Next discussions
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Missing signoff in the kvm-arm-fixes tree
Date: Tue, 21 Jul 2026 13:02:19 +0100	[thread overview]
Message-ID: <86wluoeek4.wl-maz@kernel.org> (raw)
In-Reply-To: <al9cA4bfywF11OmQ@sirena.org.uk>

On Tue, 21 Jul 2026 12:46:11 +0100,
Mark Brown <broonie@kernel.org> wrote:
> 
> [1  <text/plain; us-ascii (7bit)>]
> Commit
> 
>   6c13643a6f392 ("KVM: arm64: Fix hyp_trace clock disabling")
> 
> is missing a Signed-off-by from its committer

Amusing:

maz@valley-girl:~/hot-poop/arm-platforms$ b4 am -lsto - 20260715105100.3178255-1-vdonnefort@google.com | git am
Grabbing thread from lore.kernel.org/all/20260715105100.3178255-1-vdonnefort@google.com/t.mbox.gz
Analyzing 4 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
  ✓ [PATCH v2] KVM: arm64: Fix hyp_trace clock disabling
    + Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev> (✓ DKIM/linux.dev)
    + Link: https://patch.msgid.link/20260715105100.3178255-1-vdonnefort@google.com
    + Signed-off-by: Marc Zyngier <maz@kernel.org>
  ---
  ✓ Signed: DKIM/google.com
---
Total patches: 1
---
 Link: https://patch.msgid.link/20260715105100.3178255-1-vdonnefort@google.com
 Base: using specified base-commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa
       git checkout -b v2_20260715_vdonnefort_google_com a13c140cc289c0b7b3770bce5b3ad42ab35074aa
Applying: KVM: arm64: Fix hyp_trace clock disabling
maz@valley-girl:~/hot-poop/arm-platforms$ git show
commit ffb57162cb4e20971ea41320f8dd9fad7d141e9f (HEAD)
Author: Vincent Donnefort <vdonnefort@google.com>
Date:   Wed Jul 15 11:51:00 2026 +0100

    KVM: arm64: Fix hyp_trace clock disabling
    
    Fix the disable path in hyp_trace_clock_enable(), which fell through to
    re-initialize and reschedule the clock after cancelling the work. Return
    early instead.
    
    While at it, cleanup hyp_trace_clock::lock which is unused and
    hyp_trace_clock::running which is redundant: the trace_remote framework
    already serializes calls to the callback enable_tracing.
    
    Fixes: b22888917fa4 ("KVM: arm64: Sync boot clock with the nVHE/pKVM hyp")
    Signed-off-by: Vincent Donnefort <vdonnefort@google.com>

No RB, no SoB, no Link. Guess b4 is busted in some way...

BTW, could you please Cc the actual maintainers of KVM/arm64?
Christoffer has been out of that look for over 7 years now...

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2026-07-21 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 11:46 Missing signoff in the kvm-arm-fixes tree Mark Brown
2026-07-21 12:02 ` Marc Zyngier [this message]
2026-07-21 13:37   ` Mark Brown
2026-07-21 14:04     ` Marc Zyngier
2026-07-21 14:24       ` Mark Brown

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=86wluoeek4.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --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