All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] Fix vmi time header bug
Date: Mon, 12 Mar 2007 22:21:37 -0800	[thread overview]
Message-ID: <45F642F1.1040405@vmware.com> (raw)
In-Reply-To: <20070312223136.dc6969f3.akpm@linux-foundation.org>

Andrew Morton wrote:
> Really truly?   I think we have a _lot_ of declarations which omit the section
> qualifier altogether.  How come they don't all break too?
>   

According to the report I have.  Perhaps a bogus section qualifier does 
more damage than an omitted one.  I'll get gcc  / linker version, but 
this could be a combination of user error, a strange toolchain, and 
perhaps a real bug somewhere.

> (ARM (at least) in fact does require the section tagging on the declaration as
> well as the definition, but we've thus far only fixed that in a couple of places
> which were causing breakage).
>   

Yes, I was surprised by this as well, and I'm still skeptical about this 
being the real cause.  Still, this reportedly fixed the problem, and is 
certainly not a bad thing.

Zach

  reply	other threads:[~2007-03-13  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 22:58 [PATCH] Fix vmi time header bug Zachary Amsden
2007-03-13  6:31 ` Andrew Morton
2007-03-13  6:21   ` Zachary Amsden [this message]
2007-03-13  6:46   ` Zachary Amsden
2007-03-13 12:45     ` Andi Kleen
2007-03-13 13:59       ` Andrew Morton
2007-03-13 17:32         ` Jeremy Fitzhardinge
2007-03-13 17:53         ` Linus Torvalds

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=45F642F1.1040405@vmware.com \
    --to=zach@vmware.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.