From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
mbligh@google.com, fche@redhat.com,
masami.hiramatsu.pt@hitachi.com, prasanna@in.ibm.com,
akpm@osdl.org, mingo@elte.hu, lethal@linux-sh.org,
linux-kernel@vger.kernel.org, jes@sgi.com, zanussi@us.ibm.com,
richardj_moore@uk.ibm.com, michel.dagenais@polymtl.ca,
hch@infradead.org, gregkh@suse.de, tglx@linutronix.de,
wcohen@redhat.com, ltt-dev@shafik.org,
systemtap@sources.redhat.com, alan@lxorguk.ukuu.org.uk,
karim@opersys.com, pavel@suse.cz, joe@perches.com,
rdunlap@xenotime.net, jrs@us.ibm.com
Subject: Re: [PATCH] Linux Kernel Markers 0.20 for 2.6.17
Date: Tue, 17 Oct 2006 12:39:55 -0700 [thread overview]
Message-ID: <4535318B.2050408@goop.org> (raw)
In-Reply-To: <20061017191924.GA14092@Krystal>
Mathieu Desnoyers wrote:
> I guess the correct way to handle it will be to put a "used" attribute in the
> asm-generic/marker.h code, remove the unnecessary "unused" attribute in
> asm-powerpc/marker.h and tell people to upgrade their gcc when it is broken.
>
It's subtle because it quietly drops the section with no other
symptoms. It could slip by unnoticed for quite a while.
> The other way around would be to make the macro "use" the structure somewhere
> without any impact.
>
asm volatile("" : : "m" (thing));
J
prev parent reply other threads:[~2006-10-17 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 18:04 [PATCH] Linux Kernel Markers 0.20 for 2.6.17 Mathieu Desnoyers
2006-10-17 15:51 ` Atsushi Nemoto
2006-10-17 18:36 ` Jeremy Fitzhardinge
2006-10-17 19:19 ` Mathieu Desnoyers
2006-10-17 19:39 ` Jeremy Fitzhardinge [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=4535318B.2050408@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anemo@mba.ocn.ne.jp \
--cc=compudj@krystal.dyndns.org \
--cc=fche@redhat.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jes@sgi.com \
--cc=joe@perches.com \
--cc=jrs@us.ibm.com \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mbligh@google.com \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=prasanna@in.ibm.com \
--cc=rdunlap@xenotime.net \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.com \
/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