From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: binutils@sourceware.org
Cc: jose.marchesi@oracle.com, elena.zannoni@oracle.com,
cupertino.miranda@oracle.com, nickc@redhat.com
Subject: [PATCH-BPF] Fixes in recent BPF commit
Date: Fri, 17 Mar 2023 16:00:43 +0000 [thread overview]
Message-ID: <20230317160045.502282-1-cupertino.miranda@oracle.com> (raw)
Hi Jose, Nick,
The patches below fix a problem detected by the tests, as well as an
update to the tests based on the changes made in BPF relocations.
BPF ld is currently broken without the first patch.
Looking forward to your review as quickly as you can.
Best regards,
Cupertino
next reply other threads:[~2023-03-17 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:00 Cupertino Miranda [this message]
2023-03-17 16:00 ` [PATCH 1/2] Reloc howto access broken for BPF Cupertino Miranda
2023-03-17 16:00 ` [PATCH 2/2] Changed ld and gas BPF tests Cupertino Miranda
2023-03-20 14:57 ` Jose E. Marchesi
2023-03-20 15:31 ` Cupertino Miranda
2023-03-20 16:01 ` Jose E. Marchesi
2023-03-20 11:34 ` [PATCH-BPF] Fixes in recent BPF commit Nick Clifton
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=20230317160045.502282-1-cupertino.miranda@oracle.com \
--to=cupertino.miranda@oracle.com \
--cc=binutils@sourceware.org \
--cc=elena.zannoni@oracle.com \
--cc=jose.marchesi@oracle.com \
--cc=nickc@redhat.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).