stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Chikunov <vt@altlinux.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	"Dmitry V. Levin" <ldv@altlinux.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] tools lib: Fix builds when glibc contains strlcpy
Date: Mon, 30 Dec 2019 20:03:04 +0300	[thread overview]
Message-ID: <20191230170304.btdoxtmods7d6ctq@altlinux.org> (raw)
In-Reply-To: <20191230005604.4FFA9207FF@mail.kernel.org>

Sasha,

On Mon, Dec 30, 2019 at 12:56:03AM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: ce99091730c9 ("perf tools: Move strlcpy() from perf to tools/lib/string.c").
> 
> The bot has tested the following trees: v5.4.6, v5.3.18, v4.19.91, v4.14.160, v4.9.207.
> 
> v5.4.6: Build OK!
> v5.3.18: Build OK!
> v4.19.91: Failed to apply! Possible dependencies:
>     7bd330de43fd ("tools lib: Adopt skip_spaces() from the kernel sources")
> 
> v4.14.160: Failed to apply! Possible dependencies:
>     7bd330de43fd ("tools lib: Adopt skip_spaces() from the kernel sources")
> 
> v4.9.207: Failed to apply! Possible dependencies:
>     7bd330de43fd ("tools lib: Adopt skip_spaces() from the kernel sources")
>     96395cbbc7e9 ("tools lib string: Adopt prefixcmp() from perf and subcmd")
> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?

Yes, there is a trivial conflict when this patch is applied to stable trees.
Do you need any help in resolving it?

Thanks,


  parent reply	other threads:[~2019-12-30 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 17:20 [PATCH v3] tools lib: Fix builds when glibc contains strlcpy Vitaly Chikunov
     [not found] ` <20191230005604.4FFA9207FF@mail.kernel.org>
2019-12-30 17:03   ` Vitaly Chikunov [this message]
2020-01-10 17:53 ` [tip: perf/core] tools lib: Fix builds when glibc contains strlcpy() tip-bot2 for Vitaly Chikunov

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=20191230170304.btdoxtmods7d6ctq@altlinux.org \
    --to=vt@altlinux.org \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=jpoimboe@redhat.com \
    --cc=ldv@altlinux.org \
    --cc=sashal@kernel.org \
    --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).