From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: Use generic BUG() handler
Date: Wed, 6 Jul 2011 21:06:07 +0100 [thread overview]
Message-ID: <20110706200607.GS8286@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTikHT2E=76jMLbzmQm_CiUw8rA3cCA@mail.gmail.com>
On Thu, May 19, 2011 at 10:24:31PM -0700, Simon Glass wrote:
> On Mon, Apr 25, 2011 at 6:47 PM, Olof Johansson <olof@lixom.net> wrote:
> > On Wed, Apr 20, 2011 at 11:01:59AM -0700, Stephen Boyd wrote:
> >
> >> It's here:
> >> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6885/1
> >>
> >> I imagine it will be added when/if Russell picks it up. Sadly it
> >> increases the LOC in ARM so Simon might need to really
> >> sell it to get it merged.
> >
> > It's core code though, and the concern today is not with ARM core code
> > as much as with the various platforms that are growing seemingly without
> > upper bounds.
>
> Hi,
>
> Can anyone advise please what happens next with this patch? So far I
> have posted it to the list, it has been reviewed on the list and I
> have put it into the patch system. What is the next step please to get
> this into the kernel?
Sorry, I've finally got back to looking at this.
+ ".pushsection .rodata.str, \"aMS\", 1\n" \
According to my gas manual:
| 7.88 `.pushsection NAME [, SUBSECTION] [, "FLAGS"[, @TYPE[,ARGUMENTS]]]'
| ...
| This directive pushes the current section (and subsection) onto the
| top of the section stack, and then replaces the current section and
| subsection with `name' and `subsection'. The optional `flags', `type'
| and `arguments' are treated the same as in the `.section' (*note
| Section::) directive.
|
| 7.94 `.section NAME'
| ...
| ELF Version
| ...
| Note on targets where the `@' character is the start of a comment (eg
| ARM) then another character is used instead. For example the ARM port
| uses the `%' character.
|
| If FLAGS contains the `M' symbol then the TYPE argument must be
| specified as well as an extra argument--ENTSIZE--like this:
|
| .section NAME , "FLAGS"M, @TYPE, ENTSIZE
|
| Sections with the `M' flag but not `S' flag must contain fixed size
| constants, each ENTSIZE octets long. Sections with both `M' and `S'
| must contain zero terminated strings where each character is ENTSIZE
| bytes long. The linker may remove duplicates within sections with the
| same name, same entity size and same flags. ENTSIZE must be an
| absolute expression.
It appears that the TYPE argument is missing. As the GAS manual says
its required, then I think it really ought to be there. Any comment?
next prev parent reply other threads:[~2011-07-06 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 23:00 [PATCH v4] ARM: Use generic BUG() handler Simon Glass
2011-04-15 2:10 ` Stephen Boyd
2011-04-20 2:40 ` Simon Glass
2011-04-20 4:43 ` anish singh
2011-04-20 18:01 ` Stephen Boyd
2011-04-20 18:37 ` Ramirez Luna, Omar
2011-04-26 1:47 ` Olof Johansson
2011-05-20 5:24 ` Simon Glass
2011-07-06 20:06 ` Russell King - ARM Linux [this message]
2011-07-07 9:28 ` Dave Martin
2011-07-12 0:01 ` Simon Glass
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=20110706200607.GS8286@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).