All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v5] lib/string.c: implement stpcpy
Date: Thu, 17 Sep 2020 15:53:32 +0000	[thread overview]
Message-ID: <20200917155332.E0EFF20872@mail.kernel.org> (raw)
In-Reply-To: <20200914161643.938408-1-ndesaulniers@google.com>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.8.9, v5.4.65, v4.19.145, v4.14.198, v4.9.236, v4.4.236.

v5.8.9: Build OK!
v5.4.65: Build OK!
v4.19.145: Failed to apply! Possible dependencies:
    458a3bf82df4 ("lib/string: Add strscpy_pad() function")

v4.14.198: Failed to apply! Possible dependencies:
    458a3bf82df4 ("lib/string: Add strscpy_pad() function")

v4.9.236: Failed to apply! Possible dependencies:
    458a3bf82df4 ("lib/string: Add strscpy_pad() function")

v4.4.236: Failed to apply! Possible dependencies:
    458a3bf82df4 ("lib/string: Add strscpy_pad() function")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

      parent reply	other threads:[~2020-09-17 18:54 UTC|newest]

Thread overview: 8+ 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
2020-09-17 15:53   ` Sasha Levin [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=20200917155332.E0EFF20872@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=keescook@chromium.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.