From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [GIT PULL] x86 PTI and Spectre related fixes and updates
Date: Thu, 15 Feb 2018 06:48:36 +0100 [thread overview]
Message-ID: <20180215054836.GA9861@kroah.com> (raw)
In-Reply-To: <CA+55aFy-TRt++ujpxdq3U5mmXaKLW+jXuB=eD=KWY_Lsz+ox5w@mail.gmail.com>
On Wed, Feb 14, 2018 at 05:17:25PM -0800, Linus Torvalds wrote:
> On Wed, Feb 14, 2018 at 4:38 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > This tree generates two relatively simple conflicts with your tree:
>
> So what annoys me about these conflicts is that I'm not convinced that
> the stable tree actually *uses* your fancy x86/pti branch?
>
> I think stable ends up working like a patch-queue anyway due to how
> Greg works and all his helper scripts, so the whole "let's keep a
> branch for pti" ends up being of dubious advantage when it results in
> conflicts on merging, and it's not the same commits in the end anyway.
I do use it, I take the commits from there and then queue them up as
individual patches for the stable releases.
And if it wasn't there, the conflict resolution would have to be on my
side, making them "not the same commits in the end", so either I have to
do that, or you do :)
> This is not a complaint so much as a "is it worth it?" question..
So far, I think this is the first conflict it's generated in a long
time, so previously it was worth it from my point of view. As long as
it doesn't cause more work for the TIP maintainers, or for you, I
appreciate it. But if it does cause more work, don't worry about it, I
can handle backporting things as needed.
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-15 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 0:38 [GIT PULL] x86 PTI and Spectre related fixes and updates Ingo Molnar
2018-02-15 1:17 ` Linus Torvalds
2018-02-15 5:48 ` Greg Kroah-Hartman [this message]
2018-02-15 8:03 ` Ingo Molnar
2018-02-15 8:16 ` Ingo Molnar
2018-02-15 17:04 ` Linus Torvalds
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=20180215054836.GA9861@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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