From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [uClinux-dev] [PATCH] Valid relocation symbol for FLAT format on ARM, v2
Date: Sat, 2 Jan 2010 23:07:08 +0000 [thread overview]
Message-ID: <20100102230708.GA32298@shareable.org> (raw)
In-Reply-To: <201001010123.49951.vapier@gentoo.org>
Mike Frysinger wrote:
> when posting updates, you should put the "v2" and such inside of the
> "[patch]" marker like so: [PATCH v2]. git will remove this
> automatically when applying.
Thanks; I didn't know this.
> On Thursday 31 December 2009 20:26:45 Jun Sun wrote:
> > #define flat_old_ram_flag(flags) (flags)
> > -#define flat_reloc_valid(reloc, size) ((reloc) <= (size))
> > +#define flat_reloc_valid(reloc, size) ((reloc) <= (size) + 0x1000)
> > +/* [jsun] new gcc 4.x generates ANCHOR symbols in order to reduce the size
>
> comments go above the thing they're documenting, not below. the "[jsun]" is
> also not really useful -- no one who reads this after the fact will have any
> idea what "[jsun]" means.
I agree with everything Mike said. Put the comment before the
#define, and lose the "[jsun]". If someone wants to know who wrote
the comment they can use "git blame" and get your full email address.
Actually I'd go a bit further: I think it's be tidier to put the
comment and #define in their own block, separated by a blank line from
the other #defines.
I don't see how GCC can make the GOT smaller with relocs pointing
_after_ the end of the BSS (middle yes, but after?), but given that it
does, the patch looks good to me.
-- Jamie
next prev parent reply other threads:[~2010-01-02 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 1:26 [PATCH] Valid relocation symbol for FLAT format on ARM, v2 Jun Sun
2010-01-01 6:23 ` [uClinux-dev] " Mike Frysinger
2010-01-02 23:07 ` Jamie Lokier [this message]
2010-01-02 23:09 ` Jamie Lokier
2010-01-04 18:58 ` Jun Sun
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=20100102230708.GA32298@shareable.org \
--to=jamie@shareable.org \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).