From: Shaohua Li <shaohua.li@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Adam Belay <ambx1@neo.rr.com>,
Matthieu Castet <castet.matthieu@free.fr>,
acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PNPACPI: fix types when decoding ACPI resources [resend]
Date: Wed, 03 Aug 2005 09:01:01 +0800 [thread overview]
Message-ID: <1123030861.2937.4.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <200508020955.54844.bjorn.helgaas@hp.com>
On Tue, 2005-08-02 at 09:55 -0600, Bjorn Helgaas wrote:
> Any objections to the patch below? I posted it last Wednesday,
> but haven't heard anything. Once we have this fix, 8250_pnp
> should have sufficient functionality that we can get rid of
> 8250_acpi.
>
>
>
> Use types that match the ACPI resource structures. Previously
> the u64 value from an RSTYPE_ADDRESS64 was passed as an int,
> which corrupts the value.
>
> This is one of the things that prevents 8250_pnp from working
> on HP ia64 boxes. After 8250_pnp works, we will be able to
> remove 8250_acpi.c.
We might always use 'unsigned long'. Did you have plan to remove other
legacy acpi drivers?
Thanks,
Shaohua
next prev parent reply other threads:[~2005-08-03 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 15:55 [PATCH] PNPACPI: fix types when decoding ACPI resources [resend] Bjorn Helgaas
2005-08-03 1:01 ` Shaohua Li [this message]
2005-08-03 15:20 ` [ACPI] " Bjorn Helgaas
2005-08-03 21:16 ` matthieu castet
2005-08-03 21:41 ` Bjorn Helgaas
2005-08-04 12:38 ` matthieu castet
2005-08-04 15:57 ` Bjorn Helgaas
2005-08-04 16:08 ` matthieu castet
2005-08-04 0:51 ` Shaohua Li
2005-08-28 17:40 ` matthieu castet
2005-08-04 0:46 ` Shaohua Li
2005-08-03 1:05 ` [ACPI] " Kenji Kaneshige
2005-08-03 18:29 ` Bjorn Helgaas
2005-08-04 5:18 ` Kenji Kaneshige
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=1123030861.2937.4.camel@linux-hp.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox