From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Namhyung Kim <namhyung@gmail.com>,
stable@vger.kernel.org, Akemi Yagi <toracat@elrepo.org>
Subject: Re: 6.5-stable backport request
Date: Thu, 5 Oct 2023 15:23:15 -0300 [thread overview]
Message-ID: <ZR7/E4KKl0q7NBUX@kernel.org> (raw)
In-Reply-To: <ZRv6IFKjB+KMr6CH@sashalap>
Em Tue, Oct 03, 2023 at 07:25:20AM -0400, Sasha Levin escreveu:
> On Thu, Sep 28, 2023 at 01:41:34PM -0700, Namhyung Kim wrote:
> > Hello,
> >
> > Please queue up this commit for 6.5-stable:
> >
> > * commit: 88cc47e24597971b05b6e94c28a2fc81d2a8d61a
> > ("perf build: Define YYNOMEM as YYNOABORT for bison < 3.81")
> > * Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > The recent change v6.5 series added YYNOMEM changes
> > in the perf tool and it caused a build failure on machines with
> > older bison. The above commit should be applied to fix it.
>
> Queued up, thanks!
Thanks a lot!
- Arnaldo
prev parent reply other threads:[~2023-10-05 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 20:41 6.5-stable backport request Namhyung Kim
2023-10-03 11:25 ` Sasha Levin
2023-10-05 18:23 ` Arnaldo Carvalho de Melo [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=ZR7/E4KKl0q7NBUX@kernel.org \
--to=acme@kernel.org \
--cc=namhyung@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=toracat@elrepo.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