All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "the arch/x86 maintainers" <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] x86: TLS regression fixes
Date: Fri, 23 Jan 2015 07:56:35 +1200	[thread overview]
Message-ID: <CA+55aFyQ9zfeNoboW_ypYoKCO55CM_9X0Qgi5NkU4AAqSmPuWQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1421954363.git.luto@amacapital.net>

On Fri, Jan 23, 2015 at 7:27 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>
> Thoughts?

Looks good to me.

And since I curse at people who ignore regression reports because "it
fixes a bug", I should take the time to say how much I liked seeing
you explain to the people who reported this regression why it happened
and what the thinking was. Now *that* is how things should work. "My
bad, this was the background for why it seemed like a good idea".

And I guess the second patch should also be marked for stable, since
the thing that causes problems got backported too.

                 Linus

      parent reply	other threads:[~2015-01-22 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 19:27 [PATCH 0/2] x86: TLS regression fixes Andy Lutomirski
2015-01-22 19:27 ` [PATCH 1/2] x86, tls, ldt: Stop checking lm in LDT_empty Andy Lutomirski
2015-01-22 20:13   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2015-01-22 19:27 ` [PATCH 2/2] x86, tls: Interpret an all-zero struct user_desc as "no segment" Andy Lutomirski
2015-01-22 19:47   ` Borislav Petkov
2015-01-22 20:12     ` Andy Lutomirski
2015-01-22 20:14   ` [tip:x86/urgent] x86, tls: Interpret an all-zero struct user_desc as %22no segment%22 tip-bot for Andy Lutomirski
2015-01-22 20:54   ` [tip:x86/urgent] x86, tls: Interpret an all-zero struct user_desc as "no segment" tip-bot for Andy Lutomirski
2015-01-22 19:56 ` Linus Torvalds [this message]

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=CA+55aFyQ9zfeNoboW_ypYoKCO55CM_9X0Qgi5NkU4AAqSmPuWQ@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.