mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	linux-kernel@vger.kernel.org, Richard Henderson <rth@twiddle.net>,
	Dave Jones <davej@redhat.com>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>, Andi Kleen <ak@suse.de>,
	Raj Ashok <ashok.raj@intel.com>
Subject: Re: [PATCH] alpha build pm_power_off hack
Date: Sun, 11 Dec 2005 22:23:12 -0700	[thread overview]
Message-ID: <m1y82qany7.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051211232428.18286.40968.sendpatchset@sam.engr.sgi.com> (Paul Jackson's message of "Sun, 11 Dec 2005 15:24:29 -0800 (PST)")

Paul Jackson <pj@sgi.com> writes:

> This follows up Eric W. Biederman's patch of Dec 8, 2005:
>   [PATCH] Don't attempt to power off if power off is not implemented.
>
> To avoid having problems with one arch break the crosstool
> builds which developers for other arch's do to ensure they
> haven't added an arch-specific build bug, add a NULL
> pm_power_off() function pointer definition to the alpha build.
>
> Without this change, an alpha build fails in the final link
> stage, for the missing 'pm_power_off' symbol that is used
> in kernel/sys.c
>
> If the alpha developers don't like the behaviour of '/sbin/halt'
> on their kernel, I will leave that to them to figure out.

Taking a quick glance at alpha causes me to think we always
want pm_power_off to be non null on alpha.

Eric

  reply	other threads:[~2005-12-12  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11 23:24 Paul Jackson
2005-12-12  5:23 ` Eric W. Biederman [this message]
2005-12-12  6:24   ` Paul Jackson
2005-12-12 12:10     ` Eric W. Biederman
2005-12-12 13:44       ` Ivan Kokshaysky

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=m1y82qany7.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=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=rth@twiddle.net \
    --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

Powered by JetHome