From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: PATCH: Add CR16 support to readelf and replace NUM_ELEM with ARRAY_SIZE
Date: Tue, 24 Jul 2007 12:32:00 -0000 [thread overview]
Message-ID: <m3odi2nfxe.fsf@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Hi Guys,
I am being a bit naughty here by combining three patches to readelf
into one submission...
I am applying the attached patch to fix a couple of minor things
with readelf. The first was that it did not recognize the newly
added CR16 target. The second was that there is no need for the
NUM_ELEM() macro since a standard alternative version - ARRAY_SIZE
- is defined in libiberty.h. Finally the third fix is to correct a
few formatting errors in recently added code.
Cheers
Nick
binutils/ChangeLog
2007-07-24 Nick Clifton <nickc@redhat.com>
* readelf.c (NUM_ELEM): Remove redundant macro; replace references
to it with references to ARRAY_SIZE.
Add support for CR16.
Fix formatting.
[-- Attachment #2: readelf.c.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 3014 bytes --]
next reply other threads:[~2007-07-24 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 12:32 Nick Clifton [this message]
2007-07-24 14:10 ` M R Swami Reddy
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=m3odi2nfxe.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@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).