From: Arnaldo Carvalho de Melo <acme@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the tip tree
Date: Thu, 7 Dec 2017 09:27:16 -0200 [thread overview]
Message-ID: <20171207112716.GB3138@redhat.com> (raw)
In-Reply-To: <20171207094016.32774ae8@canb.auug.org.au>
Em Thu, Dec 07, 2017 at 09:40:16AM +1100, Stephen Rothwell escreveu:
> Hi all,
>
> Commit
>
> 0b44cfb8e40f ("tools/headers: Synchronize kernel x86 UAPI headers")
>
> is missing a Signed-off-by from its committer.
oops, my bad :-\ I'll avoid this in the future with scripts before
pushing to Ingo.
- Arnaldo
commit 0b44cfb8e40f64cd72520be223414a7ef79c5d90
Author: Ingo Molnar <mingo@kernel•org>
AuthorDate: Sat Nov 18 09:00:46 2017 +0100
Commit: Arnaldo Carvalho de Melo <acme@redhat•com>
CommitDate: Tue Nov 28 14:29:05 2017 -0300
tools/headers: Synchronize kernel x86 UAPI headers
Two x86 headers got modified in this merge window:
arch/x86/include/asm/cpufeatures.h
arch/x86/include/asm/disabled-features.h
To support x86 UMIP feature, to add new AVX instructions, plus
cleanups.
None of those changes have an effect on tooling, so do a plain copy.
Cc: Arnaldo Carvalho de Melo <acme@redhat•com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Cc: Linus Torvalds <torvalds@linux-foundation•org>
Cc: Peter Zijlstra <peterz@infradead•org>
Cc: Thomas Gleixner <tglx@linutronix•de>
Cc: Peter Zijlstra <peterz@infradead•org>
Cc: Namhyung Kim <namhyung@kernel•org>
Cc: Jiri Olsa <jolsa@redhat•com>
Cc: linux-kernel@vger•kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel•org>
next prev parent reply other threads:[~2017-12-07 11:27 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 22:40 linux-next: Signed-off-by missing for commit in the tip tree Stephen Rothwell
2017-12-07 11:27 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-19 20:06 Stephen Rothwell
2017-12-21 10:25 ` Thomas Gleixner
2017-12-21 10:55 ` Stephen Rothwell
2017-12-29 23:44 Stephen Rothwell
2017-12-30 8:20 ` Ingo Molnar
2018-01-28 21:21 Stephen Rothwell
2018-02-18 8:25 Stephen Rothwell
2018-07-22 21:54 Stephen Rothwell
2018-09-06 21:26 Stephen Rothwell
2018-09-06 21:39 ` Thomas Gleixner
2019-06-25 23:32 Stephen Rothwell
2019-06-26 5:18 ` Thomas Gleixner
2019-12-04 10:08 Stephen Rothwell
2020-02-20 20:03 Stephen Rothwell
2020-02-20 20:20 ` Borislav Petkov
2020-04-23 8:18 Stephen Rothwell
2020-05-04 8:58 Stephen Rothwell
2020-06-11 21:21 Stephen Rothwell
2020-12-10 10:52 Stephen Rothwell
2020-12-10 12:50 ` Giovanni Gherdovich
2020-12-10 13:02 ` Peter Zijlstra
2021-12-05 14:46 Stephen Rothwell
2021-12-19 21:14 Stephen Rothwell
2021-12-19 21:49 ` Borislav Petkov
2022-03-03 9:48 Stephen Rothwell
2022-03-12 6:01 Stephen Rothwell
2022-05-12 10:44 Stephen Rothwell
2022-05-12 14:31 ` Peter Zijlstra
2022-05-25 22:28 Stephen Rothwell
2022-05-26 2:42 ` Ingo Molnar
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
2023-09-17 22:01 Stephen Rothwell
2024-01-31 20:41 Stephen Rothwell
2024-01-31 20:58 ` Borislav Petkov
2024-05-21 23:04 Stephen Rothwell
2024-07-01 10:03 Stephen Rothwell
2024-07-01 10:58 ` Peter Zijlstra
2024-08-18 22:09 Stephen Rothwell
2024-08-20 16:41 ` Thomas Gleixner
2024-10-28 20:50 Stephen Rothwell
2024-10-29 12:53 ` Peter Zijlstra
2025-02-04 21:00 Stephen Rothwell
2025-02-05 9:14 ` Peter Zijlstra
2025-02-05 9:33 ` Peter Zijlstra
2025-06-28 22:09 Stephen Rothwell
2025-07-02 22:49 Stephen Rothwell
2025-07-14 21:47 Stephen Rothwell
2025-07-14 22:06 ` Borislav Petkov
2025-11-16 19:49 Stephen Rothwell
2025-11-16 20:01 ` Borislav Petkov
2025-11-30 19:27 Stephen Rothwell
2025-12-01 5:57 ` Ingo Molnar
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=20171207112716.GB3138@redhat.com \
--to=acme@redhat$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/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