From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnaldo Carvalho de Melo <acme@kernel•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail•com>,
Namhyung Kim <namhyung@kernel•org>,
Ruffalo Lavoisier <ruffalolavoisier@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: Tue, 17 Dec 2024 11:39:47 +1100 [thread overview]
Message-ID: <20241217113947.0ad90c47@canb.auug.org.au> (raw)
In-Reply-To: <Z2DG41WOlZgQl9Ue@x1>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
Hi Arnaldo,
On Mon, 16 Dec 2024 21:33:39 -0300 Arnaldo Carvalho de Melo <acme@kernel•org> wrote:
>
> I can force push after the original author provides the Signed-off-by,
> but for such a simple patch can we just keep things as-is?
>
> Is that that what you're saying?
Yeah, hardly worth a rebase/rewrite.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-12-17 0:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 21:27 linux-next: Signed-off-by missing for commit in the perf tree Stephen Rothwell
2024-12-17 0:33 ` Arnaldo Carvalho de Melo
2024-12-17 0:39 ` Stephen Rothwell [this message]
2024-12-17 0:55 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 22:24 Stephen Rothwell
2025-12-04 22:52 ` Ian Rogers
2025-12-04 23:41 ` Namhyung Kim
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=20241217113947.0ad90c47@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=acme@kernel$(echo .)org \
--cc=arnaldo.melo@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=namhyung@kernel$(echo .)org \
--cc=ruffalolavoisier@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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