From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: Nick Clifton <nickc@redhat.com>, Alan Modra <amodra@gmail.com>
Subject: [PATCH 0/2] gas/ELF: allow "inheriting" section attributes and type
Date: Mon, 14 Aug 2023 15:47:28 +0200 [thread overview]
Message-ID: <9ccf6770-66bd-c924-93e1-fd54a6daf610@suse.com> (raw)
I'm a little uncertain with how easy it (apparently) was to make the
intended change in patch 1, so I fear I'm overlooking something. Input
would be much appreciated.
The 2nd patch here is merely some cleanup I found desirable to do while
adding the new test in patch 1.
1: allow "inheriting" section attributes and type
2: widen use of $dump_opts in testsuite
Jan
next reply other threads:[~2023-08-14 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 13:47 Jan Beulich [this message]
2023-08-14 13:48 ` [PATCH 1/2] " Jan Beulich
2023-08-14 13:48 ` [PATCH 2/2] gas/ELF: widen use of $dump_opts in testsuite Jan Beulich
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=9ccf6770-66bd-c924-93e1-fd54a6daf610@suse.com \
--to=jbeulich@suse.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--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).