From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Rename bfd_bread and bfd_bwrite
Date: Tue, 15 Aug 2023 12:02:24 +0200 [thread overview]
Message-ID: <CAJVr-EOV8Gq5n+OvwC32CgVqQ61jiFRY7PaN8SO0PKv67ngTqA@mail.gmail.com> (raw)
In-Reply-To: <ZNLOzSRCvRcYQzn7@squeak.grove.modra.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Wed, Aug 9, 2023 at 1:28 AM Alan Modra via Gdb-patches <
gdb-patches@sourceware.org> wrote:
> These were renamed from bfd_read and bfd_write back in 2001 when they
> lost an unnecessary parameter. Rename them back, and get rid of a few
> casts that are only needed without prototyped functions (K&R C).
>
>
> This patch haven't applied cleanly for me, it may need a rebase.
>
I tested it on x86_64 Fedora Rawhide and I can see no regressions.
>
>
>
>
>
>
>
>
prev parent reply other threads:[~2023-08-15 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 23:25 Alan Modra
2023-08-15 10:02 ` Alexandra Petlanova Hajkova [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=CAJVr-EOV8Gq5n+OvwC32CgVqQ61jiFRY7PaN8SO0PKv67ngTqA@mail.gmail.com \
--to=ahajkova@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
/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).