From: Matt Helsley <mhelsley@vmware.com>
To: Julien Thierry <jthierry@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <jpoimboe@redhat.com>,
<peterz@infradead.org>, <mbenes@suse.cz>
Subject: Re: [PATCH v2 1/4] objtool: Move object file loading out of check
Date: Mon, 8 Jun 2020 11:49:24 -0700 [thread overview]
Message-ID: <20200608184924.GA1284251@rlwimi.vmware.com> (raw)
In-Reply-To: <20200608071203.4055-2-jthierry@redhat.com>
On Mon, Jun 08, 2020 at 08:12:00AM +0100, Julien Thierry wrote:
> Structure objtool_file can be used by different subcommands. In fact
> it already is, by check and orc.
>
> Provide a function that allows to initialize objtool_file, that builtin
> can call, without relying on check to do the correct setup for them and
> explicitly hand the objtool_file to them.
>
> Signed-off-by: Julien Thierry <jthierry@redhat.com>
Reviewed-by: Matt Helsley <mhelsley@vmware.com>
> ---
> tools/objtool/builtin-check.c | 7 ++++++-
> tools/objtool/builtin-orc.c | 8 +++++++-
> tools/objtool/check.c | 37 +++++++++++------------------------
> tools/objtool/objtool.c | 29 +++++++++++++++++++++++++++
> tools/objtool/objtool.h | 4 +++-
> tools/objtool/weak.c | 4 +---
> 6 files changed, 57 insertions(+), 32 deletions(-)
next prev parent reply other threads:[~2020-06-08 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 7:11 [PATCH v2 0/4] Remove dependency of check subcmd upon orc Julien Thierry
2020-06-08 7:12 ` [PATCH v2 1/4] objtool: Move object file loading out of check Julien Thierry
2020-06-08 18:49 ` Matt Helsley [this message]
2020-06-08 7:12 ` [PATCH v2 2/4] objtool: Move orc outside " Julien Thierry
2020-06-08 18:50 ` Matt Helsley
2020-06-08 7:12 ` [PATCH v2 3/4] objtool: orc: Skip setting orc_entry for non-text sections Julien Thierry
2020-06-08 7:12 ` [PATCH v2 4/4] objtool: orc_gen: Move orc_entry out of instruction structure Julien Thierry
2020-06-09 9:44 ` [PATCH v2 0/4] Remove dependency of check subcmd upon orc Miroslav Benes
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=20200608184924.GA1284251@rlwimi.vmware.com \
--to=mhelsley@vmware.com \
--cc=jpoimboe@redhat.com \
--cc=jthierry@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--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