linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Veronika Molnarova <vmolnaro@redhat.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the perf tree
Date: Thu, 14 Sep 2023 19:50:54 -0700	[thread overview]
Message-ID: <CAM9d7chQmD2RRazcC+R6SgJtx8OoEEuSS6CkzCuTJAFKy0-TtA@mail.gmail.com> (raw)
In-Reply-To: <20230915072642.74e3c00f@canb.auug.org.au>

Hello Stephen,

On Thu, Sep 14, 2023 at 2:26 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Commits
>
>   19d8ab40f89b ("perf test stat+shadow_stat.sh: Add threshold for rounding errors")
>   0c4ded92280b ("perf test lock_contention.sh: Skip test if the number of CPUs is low")
>
> are missing a Signed-off-by from their author.

Thanks for the notice.  As they're recently added, I think I can replace them
with new commits with s-o-b from the author and force-push.

Veronika, can you resend those two commits with your Sign-off?

Thanks,
Namhyung

  reply	other threads:[~2023-09-15  2:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 21:26 linux-next: Signed-off-by missing for commit in the perf tree Stephen Rothwell
2023-09-15  2:50 ` Namhyung Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-05 22:14 Stephen Rothwell
2023-12-06 12:33 ` Arnaldo Carvalho de Melo
2022-12-13 21:34 Stephen Rothwell
2022-12-13 21:36 ` Arnaldo Carvalho de Melo
2022-12-13 21:40   ` Ian Rogers
2022-10-30 20:45 Stephen Rothwell
2022-10-31 14:04 ` Arnaldo Carvalho de Melo

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=CAM9d7chQmD2RRazcC+R6SgJtx8OoEEuSS6CkzCuTJAFKy0-TtA@mail.gmail.com \
    --to=namhyung@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vmolnaro@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).