All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "Chen, Justin" <justin.chen@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	"Chiang, Alexander" <achiang@hp.com>,
	"kristen.c.accardi@intel.com" <kristen.c.accardi@intel.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] acpiphp: Match the variable types for ia64
Date: Fri, 12 Sep 2008 12:32:13 -0600	[thread overview]
Message-ID: <20080912183213.GH10844@parisc-linux.org> (raw)
In-Reply-To: <B57D568CB82B0C4B897F9CD9862DE8B733A328E8E0@GVW1097EXB.americas.hpqcorp.net>

On Fri, Sep 12, 2008 at 05:03:50PM +0000, Chen, Justin wrote:
> >>                 slot->device = device;
> >> -               slot->sun = sun;
> >> +               slot->sun = (u64) sun;
> >
> >No ... the right thing to do here is make the local variable
> >'sun' a u64.  adr ought to be a u32, not an unsigned long.
> 
> If I understand your concern right, you want to change the local
> variable 'sun' in the routine register_slot() in the file acpiphp_glue.c
> from unsigned long to u64.  If that's the case, it will introduce the
> other issue that since the 'sun' is passed as the argument 4 of the
> routine acpi_evaluate_integer() and it is taking the unsigned long,
> what's the point to define 'sun' in u64?

Ooh, I think you've found a bug in the ACPI-CA.

Consider this:

/*
 * Acpi integer width. In ACPI version 1, integers are 32 bits.  In ACPI
 * version 2, integers are 64 bits. Note that this pertains to the ACPI integer
 * type only, not other integers used in the implementation of the ACPI CA
 * subsystem.
 */
typedef unsigned long long acpi_integer;

and compare and contrast it with this:

acpi_status
acpi_evaluate_integer(acpi_handle handle,
                      acpi_string pathname,
                      struct acpi_object_list *arguments, unsigned long *data);

I would argue 'data' should be an 'acpi_integer *', not an 'unsigned long *'
Len?

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

       reply	other threads:[~2008-09-12 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200510232100.j9NL0MWA030225@shell0.pdx.osdl.net>
     [not found] ` <20080910002011.GF2772@parisc-linux.org>
     [not found]   ` <20080910074940.GA12737@ldl.fc.hp.com>
     [not found]     ` <200809101103.55222.jbarnes@virtuousgeek.org>
     [not found]       ` <B57D568CB82B0C4B897F9CD9862DE8B733A328DF9E@GVW1097EXB.americas.hpqcorp.net>
     [not found]         ` <20080911104345.GL2772@parisc-linux.org>
     [not found]           ` <B57D568CB82B0C4B897F9CD9862DE8B733A328E8E0@GVW1097EXB.americas.hpqcorp.net>
2008-09-12 18:32             ` Matthew Wilcox [this message]
2008-09-12 19:12               ` [PATCH] acpiphp: Match the variable types for ia64 Moore, Robert
2008-09-15 18:45                 ` Matthew Wilcox
2008-09-24 18:55                   ` Matthew Wilcox
2008-10-10  6:20                   ` Len Brown

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=20080912183213.GH10844@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=achiang@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=justin.chen@hp.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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.