From: ebiederm@xmission.com (Eric W. Biederman)
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: schwab@suse.de, akpm@osdl.org, linux-kernel@vger.kernel.org,
pj@sgi.com, rth@twiddle.net, davej@redhat.com,
zwane@arm.linux.org.uk, ak@suse.de, ashok.raj@intel.com
Subject: Re: [PATCH] move pm_power_off and pm_idle declaration to common code
Date: Mon, 12 Dec 2005 07:54:52 -0700 [thread overview]
Message-ID: <m1ek4i9xhf.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <E1Elox7-0005lf-00@dorka.pomaz.szeredi.hu> (Miklos Szeredi's message of "Mon, 12 Dec 2005 15:46:57 +0100")
Miklos Szeredi <miklos@szeredi.hu> writes:
>> >> Does powerpc still build? A key question is how do we handle architectures
>> >> that always want to want to call machine_power_off.
>> >
>> > I didn't (and can't) check, but it should. IIRC multiple declaration
>> > of a variable is OK, as long as at most one has an initializer.
>>
>> And as long as you don't build with -fno-common.
>
> That seals the argument, since -fno-common is in linux/Makefile.
>
> So the patch wants fixing on powerpc, but I don't feel up to the task.
>
> Somebody with better knowledge of that arch?
It isn't just powerpc, alpha at least wants this behavior as well.
So until someone comes up with something better I am going to recommend
we fix the arches one at a time so we can actually audit them and
see what needs doing.
Eric
next prev parent reply other threads:[~2005-12-12 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 14:02 Miklos Szeredi
2005-12-12 14:20 ` Eric W. Biederman
2005-12-12 14:28 ` Miklos Szeredi
2005-12-12 14:36 ` Eric W. Biederman
2005-12-12 14:39 ` Andreas Schwab
2005-12-12 14:46 ` Miklos Szeredi
2005-12-12 14:54 ` Eric W. Biederman [this message]
2005-12-12 15:58 ` Paul Jackson
2005-12-12 15:26 ` [PATCH] uml: fix pm_power_off link failure Miklos Szeredi
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=m1ek4i9xhf.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=pj@sgi.com \
--cc=rth@twiddle.net \
--cc=schwab@suse.de \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®