From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: linux-sgx@vger.kernel.org
Subject: Re: [PATCH for_v29] selftests/sgx: Fix a benign linker warning
Date: Mon, 30 Mar 2020 23:35:33 +0300 [thread overview]
Message-ID: <20200330203533.GF1384380@linux.intel.com> (raw)
In-Reply-To: <20200330173120.28377-1-sean.j.christopherson@intel.com>
On Mon, Mar 30, 2020 at 10:31:20AM -0700, Sean Christopherson wrote:
> Pass a build id of "none" to the linker to suppress a warning about the
> build id being ignored:
>
> /usr/bin/ld: warning: .note.gnu.build-id section discarded, --build-id
> ignored.
>
> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Thanks. Got idea from this that the ELF format used in the test could
be further refined with something like ".note.x86.tcs", which would
contain the start offset and size of the TCS list.
/Jarkko
prev parent reply other threads:[~2020-03-30 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 17:31 [PATCH for_v29] selftests/sgx: Fix a benign linker warning Sean Christopherson
2020-03-30 20:35 ` Jarkko Sakkinen [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=20200330203533.GF1384380@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
/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).