From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Changbin Du <changbin.du@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Make perf able to build with latest libbfd
Date: Mon, 17 Feb 2020 10:25:13 +1100 [thread overview]
Message-ID: <20200217102513.2fb2c691@canb.auug.org.au> (raw)
In-Reply-To: <20200130105548.GC3841@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi Arnaldo,
On Thu, 30 Jan 2020 11:55:48 +0100 Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
>
> Em Wed, Jan 29, 2020 at 08:58:29AM +0100, Jiri Olsa escreveu:
> > On Tue, Jan 28, 2020 at 11:29:38PM +0800, Changbin Du wrote:
> > > libbfd has changed the bfd_section_* macros to inline functions
> > > bfd_section_<field> since 2019-09-18. See below two commits:
> > > o http://www.sourceware.org/ml/gdb-cvs/2019-09/msg00064.html
> > > o https://www.sourceware.org/ml/gdb-cvs/2019-09/msg00072.html
> > >
> > > This fix make perf able to build with both old and new libbfd.
> > >
> > > Signed-off-by: Changbin Du <changbin.du@gmail.com>
> >
> > Acked-by: Jiri Olsa <jolsa@redhat.com>
>
> Thanks, applied.
Just wondering if this should have been cc'd to stable?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-16 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:29 Changbin Du
2020-01-29 7:58 ` Jiri Olsa
2020-01-30 10:55 ` Arnaldo Carvalho de Melo
2020-02-16 23:25 ` Stephen Rothwell [this message]
2020-05-01 0:17 ` Joel Stanley
2020-02-05 15:45 ` [tip: perf/urgent] " tip-bot2 for Changbin Du
2020-05-31 1:50 ` [PATCH] " Marek Vasut
2020-06-01 16:47 ` Greg KH
[not found] ` <46FC68D5-0AB5-45F7-8851-555779C5685F@iscas.ac.cn>
2020-07-16 12:01 ` Greg KH
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=20200217102513.2fb2c691@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnaldo.melo@gmail.com \
--cc=changbin.du@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®