From: Borislav Petkov <bp@alien8.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
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 tip tree
Date: Wed, 31 Jan 2024 21:58:14 +0100 [thread overview]
Message-ID: <20240131205814.GMZbq0ZgKtxHZ9d4k7@fat_crate.local> (raw)
In-Reply-To: <20240201074102.00726258@canb.auug.org.au>
On Thu, Feb 01, 2024 at 07:41:33AM +1100, Stephen Rothwell wrote:
> are missing a Signed-off-by from their committer.
Yes, I decided to rebase the branch in order to have it clean from build
breakages. Lemme add my SOB to all the commits which got their SHA1s
changed in the process.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-01-31 20:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 20:41 linux-next: Signed-off-by missing for commit in the tip tree Stephen Rothwell
2024-01-31 20:58 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-17 22:01 Stephen Rothwell
2022-08-28 22:57 Stephen Rothwell
2022-08-29 2:54 ` Anshuman Khandual
2022-08-29 7:29 ` Peter Zijlstra
2022-08-29 7:46 ` Peter Zijlstra
2022-05-25 22:28 Stephen Rothwell
2022-05-26 2:42 ` Ingo Molnar
2022-05-12 10:44 Stephen Rothwell
2022-05-12 14:31 ` Peter Zijlstra
2022-03-12 6:01 Stephen Rothwell
2022-03-03 9:48 Stephen Rothwell
2021-12-19 21:14 Stephen Rothwell
2021-12-19 21:49 ` Borislav Petkov
2021-12-05 14:46 Stephen Rothwell
2020-12-10 10:52 Stephen Rothwell
2020-12-10 12:50 ` Giovanni Gherdovich
2020-12-10 13:02 ` Peter Zijlstra
2020-06-11 21:21 Stephen Rothwell
2020-05-04 8:58 Stephen Rothwell
2020-04-23 8:18 Stephen Rothwell
2020-02-20 20:03 Stephen Rothwell
2020-02-20 20:20 ` Borislav Petkov
2019-12-04 10:08 Stephen Rothwell
2019-06-25 23:32 Stephen Rothwell
2019-06-26 5:18 ` Thomas Gleixner
2018-09-06 21:26 Stephen Rothwell
2018-09-06 21:39 ` Thomas Gleixner
2018-07-22 21:54 Stephen Rothwell
2018-02-18 8:25 Stephen Rothwell
2018-02-19 15:20 ` Arnaldo Carvalho de Melo
2018-01-28 21:21 Stephen Rothwell
2017-12-29 23:44 Stephen Rothwell
2017-12-30 8:20 ` Ingo Molnar
2017-12-19 20:06 Stephen Rothwell
2017-12-21 10:25 ` Thomas Gleixner
2017-12-21 10:55 ` Stephen Rothwell
2017-12-06 22:40 Stephen Rothwell
2017-12-07 11:27 ` 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=20240131205814.GMZbq0ZgKtxHZ9d4k7@fat_crate.local \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).