From: Nick Desaulniers <ndesaulniers@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Arvind Sankar <nivedita@alum.mit.edu>,
Masahiro Yamada <masahiroy@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Sami Tolvanen <samitolvanen@google.com>,
Andy Lavr <andy.lavr@gmail.com>, Joe Perches <joe@perches.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
"# 3.4.x" <stable@vger.kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>
Subject: Re: [PATCH v5] lib/string.c: implement stpcpy
Date: Tue, 15 Sep 2020 11:13:54 -0700 [thread overview]
Message-ID: <CAKwvOdkg6MNBDfEH_A8=HRstAWFA+OcLkMkHsOLjuvSOWF9dxQ@mail.gmail.com> (raw)
In-Reply-To: <20200915042233.GA816510@ubuntu-n2-xlarge-x86>
On Mon, Sep 14, 2020 at 9:22 PM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> It would be nice to get this into mainline sooner rather than later so
> that it can start filtering into the stable trees. ToT LLVM builds have
> been broken for a month now.
Hi Andrew, I appreciate your help getting this submitted to mainline.
Noting that other folks are hitting this frequently:
https://lore.kernel.org/lkml/CAKwvOdkh=bZE6uY8zk_QePq5B3fY1ue9VjEguJ_cQi4CtZ4xgw@mail.gmail.com/
CrOS folks are already shipping v3 downstream since this is blocking
the release of their toolchain.
(Also, I appreciate folks' thoughts on the comments in the patch, but
please stop delaying this patch from hitting mainline. You can
rewrite the commit message to whatever you want, delete it for all I
care, please for god's sake please unbreak the build first).
--
Thanks,
~Nick Desaulniers
prev parent reply other threads:[~2020-09-15 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 16:09 [PATCH v4] lib/string.c: implement stpcpy Nick Desaulniers
2020-09-14 16:14 ` Nick Desaulniers
2020-09-14 16:16 ` [PATCH v5] " Nick Desaulniers
2020-09-15 4:22 ` Nathan Chancellor
2020-09-15 4:28 ` Joe Perches
2020-09-15 23:05 ` Nick Desaulniers
2020-09-15 18:13 ` Nick Desaulniers [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='CAKwvOdkg6MNBDfEH_A8=HRstAWFA+OcLkMkHsOLjuvSOWF9dxQ@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=andy.lavr@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=nivedita@alum.mit.edu \
--cc=samitolvanen@google.com \
--cc=stable@vger.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 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).