From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: Matthew Wilcox <willy@debian.org>
Cc: "Moore, Robert" <robert.moore@intel.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
"Walz, Michael" <michael.walz@intel.com>,
t-kochi@bq.jp.nec.com, linux-kernel@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] [PATCH] 1/3 ACPI resource handling
Date: Fri, 21 Feb 2003 15:36:51 -0700 [thread overview]
Message-ID: <200302211536.51368.bjorn_helgaas@hp.com> (raw)
In-Reply-To: <20030221221503.F19234@parcelfarce.linux.theplanet.co.uk>
On Friday 21 February 2003 3:15 pm, Matthew Wilcox wrote:
> On Fri, Feb 21, 2003 at 03:09:15PM -0700, Bjorn Helgaas wrote:
> > Or, since you mention a macro, maybe your question is not about
> > the usefulness of acpi_resource_to_address64() itself, but about
> > how I implemented it, namely, with the copy_field and copy_address
> > macros:
>
> Can I suggest that you do a simple memcpy() for the case where you're
> translating an address64 into an address64?
I suppose we could. Or maybe we should just get to the root of the
thing and make a generic acpi_resource_address structure and never
even expose the 16, 32, and 64 bit variants. As far as I can tell,
they just make life difficult for consumers.
Then acpi_rs_address16_resource(), acpi_rs_address32_resource(),
and acpi_rs_address64_resource() could be collapsed into one function
with pretty trivial checks for the different sizes. And there's lots
of similar collapsing that could be done. I bet we'd even find one
or two defects in the process of removing all the duplicated code.
Of course, I guess that would change the CA interface, so that
constrains things a bit.
Bjorn
next prev parent reply other threads:[~2003-02-21 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 18:25 Moore, Robert
2003-02-21 18:33 ` Bjorn Helgaas
2003-02-21 22:09 ` Bjorn Helgaas
2003-02-21 22:15 ` Matthew Wilcox
2003-02-21 22:36 ` Bjorn Helgaas [this message]
2003-02-23 22:54 ` Pavel Machek
2003-02-24 20:48 ` Folkert van Heusden
2003-02-21 23:07 Moore, Robert
2003-02-24 22:48 Moore, Robert
2003-02-25 16:57 ` Bjorn Helgaas
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=200302211536.51368.bjorn_helgaas@hp.com \
--to=bjorn_helgaas@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.walz@intel.com \
--cc=robert.moore@intel.com \
--cc=t-kochi@bq.jp.nec.com \
--cc=willy@debian.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
all inboxes | Powered by JetHome®