From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Matthias Kaehlcke <mka@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Christopher Li <sparse@chrisli.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Santos <daniel.santos@pobox.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v2] compiler.h: give up __compiletime_assert_fallback()
Date: Wed, 26 Sep 2018 11:45:19 -0700 [thread overview]
Message-ID: <CAGXu5jJaJ+1Sg3uwaZ8hzw3wFbiLrftpZDO8vdjY9_tB+P-HPQ@mail.gmail.com> (raw)
In-Reply-To: <20180926184259.GB14797@kroah.com>
On Wed, Sep 26, 2018 at 11:42 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> I'm not digging up a compiler.h patch from a web site and adding it to
> the tree this late in the release cycle. Especially given that it
> hasn't had any testing anywhere...
Good point about it not living in -next.
Who should be carrying these sorts of patches? In the past it's been
Andrew or Masahiro, yes? For linux-next, maybe it can go via -mm?
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2018-09-26 18:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 18:16 [PATCH v2] compiler.h: give up __compiletime_assert_fallback() Masahiro Yamada
2018-08-27 20:05 ` Daniel Santos
2018-08-27 20:09 ` Nick Desaulniers
2018-08-27 20:42 ` Daniel Santos
2018-08-27 21:01 ` Nick Desaulniers
2018-08-28 10:55 ` Arnd Bergmann
2018-08-28 13:46 ` Masahiro Yamada
2018-08-28 23:00 ` Nick Desaulniers
2018-08-31 16:46 ` Nick Desaulniers
2018-09-26 18:00 ` Matthias Kaehlcke
2018-09-26 18:03 ` Nick Desaulniers
2018-09-26 18:26 ` Kees Cook
2018-09-26 18:42 ` Greg KH
2018-09-26 18:45 ` Kees Cook [this message]
2018-09-26 19:03 ` Greg KH
2018-09-26 19:29 ` Nick Desaulniers
2018-09-26 19:35 ` Kees Cook
2018-10-10 6:10 ` Joel Stanley
2018-10-10 7:03 ` Miguel Ojeda
2018-10-10 14:49 ` Kees Cook
2018-10-11 2:48 ` Masahiro Yamada
2018-10-11 15:15 ` Kees Cook
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=CAGXu5jJaJ+1Sg3uwaZ8hzw3wFbiLrftpZDO8vdjY9_tB+P-HPQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.santos@pobox.com \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mka@chromium.org \
--cc=ndesaulniers@google.com \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.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 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).