From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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, 4 Dec 2025 15:41:45 -0800 [thread overview]
Message-ID: <aTIcOXF13DRLAI2q@google.com> (raw)
In-Reply-To: <CAP-5=fWf614AVPUcnf8wT04hXSpCVhfXuw7BrALUHubTPRbAPQ@mail.gmail.com>
On Thu, Dec 04, 2025 at 02:52:34PM -0800, Ian Rogers wrote:
> On Thu, Dec 4, 2025 at 2:24 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > Commit
> >
> > 6528cdd61590 ("perf tests stat: Add test for error for an offline CPU")
> >
> > is missing a Signed-off-by from its author and committer.
> >
> > I presume the original patch was truncated somehow.
>
> Yeah, there was log output that had a line starting "---"
> https://lore.kernel.org/lkml/20251203214706.112174-7-irogers@google.com/
>
> Sorry for the trouble this has caused.
> Ian
Oops, actually that's the reason I prefer having spaces in the front.
I'll take care of it and force push soon.
Thanks,
Namhyung
next prev parent reply other threads:[~2025-12-04 23:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 22:24 linux-next: Signed-off-by missing for commit in the perf tree Stephen Rothwell
2025-12-04 22:52 ` Ian Rogers
2025-12-04 23:41 ` Namhyung Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-15 21:27 Stephen Rothwell
2024-12-17 0:33 ` Arnaldo Carvalho de Melo
2024-12-17 0:39 ` Stephen Rothwell
2024-12-17 0:55 ` Arnaldo Carvalho de Melo
2023-12-05 22:14 Stephen Rothwell
2023-12-06 12:33 ` Arnaldo Carvalho de Melo
2023-09-14 21:26 Stephen Rothwell
2023-09-15 2:50 ` Namhyung Kim
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=aTIcOXF13DRLAI2q@google.com \
--to=namhyung@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).