public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-ia64@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [RFC] module to support ACPI AML calls to native firmware
Date: Wed, 19 Sep 2007 15:49:32 +0000	[thread overview]
Message-ID: <200709190949.32750.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A0274F144@scsmsx411.amr.corp.intel.com>

On Tuesday 18 September 2007 05:53:28 pm Luck, Tony wrote:
> > If you don't object to the two patches, can you incorporate them
> > as originally posted?  If you'd prefer a different approach, I'd
> > be happy to rework them, of course.
> 
> I think that adding 4K to the kernel (about 0.04% increase looking
> at a recent build ... or 0.0001% of total memory on a 4G system) isn't
> really a big deal.  I'd rather do that than export all the fw_call_*()
> functions for all the world to see.

That's certainly the most straightforward solution.  I'll post those
patches in a bit.

Bjorn

      reply	other threads:[~2007-09-19 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 23:14 [RFC] module to support ACPI AML calls to native firmware Bjorn Helgaas
2007-09-11 23:15 ` [patch 1/2] ia64: change SAL wrappers from macros to functions and export them Bjorn Helgaas
2007-09-11 23:16 ` [patch 2/2] ia64: add driver for ACPI methods to call native firmware Bjorn Helgaas
2007-09-12  8:56   ` Matthew Garrett
2007-09-12  9:48     ` Kyle McMartin
2007-09-12 16:50     ` Bjorn Helgaas
2007-09-13 23:11 ` [RFC] module to support ACPI AML calls to " Bjorn Helgaas
2007-09-18 23:53   ` Luck, Tony
2007-09-19 15:49     ` Bjorn Helgaas [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=200709190949.32750.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=tony.luck@intel.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