All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sami Tolvanen <samitolvanen@google.com>
To: Greg Hackmann <ghackmann@google.com>
Cc: gregkh@linuxfoundation.org, jb@essential.com,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Will Deacon <will.deacon@arm.com>,
	dan.rue@linaro.org, mark.brown@linaro.org, marc.zyngier@arm.com
Subject: Re: Linux 4.9.93
Date: Mon, 09 Apr 2018 20:32:57 +0000	[thread overview]
Message-ID: <CABCJKud4BrqTQXTf6x=opEKuY5LZBffaHCTN8KWKzGeoP6aOpw@mail.gmail.com> (raw)
In-Reply-To: <fbd6de8b-d2ab-9fcd-75b6-7151f24309e9@google.com>

On Mon, Apr 9, 2018 at 10:02 AM Greg Hackmann <ghackmann@google.com> wrote:
> Sami, what are the plans for upstreaming this work?

CFI is a clang-specific feature that depends on LTO. Based on the earlier
LTO discussion, we decided to collect some more evidence that clang's LTO
doesn't actually break anything in the kernel before sending out the next
revision of these patches. I will look into upstreaming this code again
once we have sufficient test coverage, hopefully by the end of the year.

Sami

  reply	other threads:[~2018-04-09 20:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09  9:05 Linux 4.9.93 Jean-Baptiste Theou
2018-04-09  9:30 ` Greg KH
2018-04-09  9:44   ` Marc Zyngier
2018-04-09  9:49   ` Ard Biesheuvel
2018-04-09  9:57     ` Jean-Baptiste Theou
2018-04-09 10:07       ` Mark Rutland
2018-04-09 10:41         ` Jean-Baptiste Theou
2018-04-09 10:25       ` Ard Biesheuvel
2018-04-09 10:28         ` Jean-Baptiste Theou
2018-04-09 11:41       ` Greg KH
2018-04-09 17:02         ` Greg Hackmann
2018-04-09 20:32           ` Sami Tolvanen [this message]
2018-04-09  9:55 ` Mark Rutland
  -- strict thread matches above, loose matches on Subject: below --
2018-04-08 15:08 Greg KH
2018-04-08 15:08 ` Greg KH

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='CABCJKud4BrqTQXTf6x=opEKuY5LZBffaHCTN8KWKzGeoP6aOpw@mail.gmail.com' \
    --to=samitolvanen@google.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=dan.rue@linaro.org \
    --cc=ghackmann@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jb@essential.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.brown@linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=will.deacon@arm.com \
    /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.