From: Florian Weimer <fweimer@redhat.com>
To: Mark Wielaard <mark@klomp.org>, libc-alpha@sourceware.org
Cc: Yonghong Song <yhs@fb.com>, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] elf.h: Add BPF relocation types.
Date: Thu, 21 Jun 2018 14:53:00 -0000 [thread overview]
Message-ID: <b4bb36f0-6ca2-9f9d-8628-ce2ee4edba96@redhat.com> (raw)
In-Reply-To: <20180616214515.10737-1-mark@klomp.org>
On 06/16/2018 11:45 PM, Mark Wielaard wrote:
> diff --git a/elf/elf.h b/elf/elf.h
> index a5b2811ce0..75043bcbf9 100644
> --- a/elf/elf.h
> +++ b/elf/elf.h
> @@ -3850,7 +3850,8 @@ enum
> /* BPF specific declarations. */
>
> #define R_BPF_NONE 0 /* No reloc */
> -#define R_BPF_MAP_FD 1 /* Map fd to pointer */
> +#define R_BPF_64_64 1
> +#define R_BPF_64_32 10
>
> /* Imagination Meta specific relocations. */
This still needs review from someone experienced with <elf.h> updates.
Thanks,
Florian
next prev parent reply other threads:[~2018-06-21 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 21:46 Mark Wielaard
2018-06-19 20:06 ` Florian Weimer
2018-06-19 20:34 ` Mark Wielaard
2018-06-19 20:38 ` Yonghong Song
2018-06-21 14:53 ` Florian Weimer [this message]
2018-06-21 15:29 ` Carlos O'Donell
2018-06-21 16:48 ` Mark Wielaard
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=b4bb36f0-6ca2-9f9d-8628-ce2ee4edba96@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=rth@twiddle.net \
--cc=yhs@fb.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).