From: Nick Clifton <nickc@redhat.com>
To: hawkinsw@obs.cr, jose.marchesi@oracle.com
Cc: binutils@sourceware.org
Subject: Missing indcall-badoperand.d
Date: Tue, 20 Feb 2024 10:35:50 +0000 [thread overview]
Message-ID: <874je3fmnt.fsf@redhat.com> (raw)
Hi Will,
Your recent commit ecd16ae4e471 appears to have omitted the new files,
resulting in an error in the gas testsuite:
ERROR: couldn't open "gas/testsuite/gas/bpf/indcall-badoperand.d": no such file or directory
Please could you check and fix the issue ? Thanks.
Cheers
Nick
next reply other threads:[~2024-02-20 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 10:35 Nick Clifton [this message]
2024-02-20 11:05 ` Jose E. Marchesi
2024-02-20 17:52 ` Will Hawkins
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=874je3fmnt.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hawkinsw@obs.cr \
--cc=jose.marchesi@oracle.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 read-only IMAP folder(s) and NNTP newsgroup(s).