From: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Keiichiro Tokunaga
<tokunaga.keiich-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Cc: Matthew E Tolentino
<matthew.e.tolentino-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
naveen.b.s-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
lhms
<lhms-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] /sys/firmware/acpi/memory/ for showing info of ACPI memory object
Date: Thu, 16 Sep 2004 10:55:11 -0700 [thread overview]
Message-ID: <1095357311.5380.253.camel@localhost> (raw)
In-Reply-To: <20040917014611.000055db.tokunaga.keiich-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
On Thu, 2004-09-16 at 09:46, Keiichiro Tokunaga wrote:
> Sorry, I sent the email in the middle of writing...
>
> On Thu, 16 Sep 2004 07:07:07 -0700, Tolentino, Matthew E wrote:
> > >I have changed the patch to create directories and files in
> > >/sys/firmware/acpi/memory/ from Dave's comments. The files are
> > >to export the following stuffs of each ACPI memory object for the
> > >first version.
> >
> > Hmm. I thought Dave's suggestion was to create an arch-agnostic
> > viewpoint of physical memory and dump it into
> > /sys/devices/system/memory in order to gain consistency between
> > arches...
>
> Yes, that is also his suggestion. I think we have agreed that there
> are arch-specific and agnostic directories. The agnostic one would
> consist of some files that the specific one provides. Actually, the
> patch is to create just the arch-specific directory. Then I would
> turn into the agnostic stuffs.
Could you explain what each of those fields means?
-- Dave
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next prev parent reply other threads:[~2004-09-16 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:07 [PATCH] /sys/firmware/acpi/memory/ for showing info of ACPI memory object Tolentino, Matthew E
[not found] ` <D36CE1FCEFD3524B81CA12C6FE5BCAB007B6FA60-oCDej+MBycNZtRGVdHMbwrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-09-16 16:00 ` Keiichiro Tokunaga
2004-09-16 16:46 ` Keiichiro Tokunaga
[not found] ` <20040917014611.000055db.tokunaga.keiich-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2004-09-16 17:55 ` Dave Hansen [this message]
2004-09-17 1:43 ` Keiichiro Tokunaga
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 10:54 [PATCH] ACPI based Memory Hotplug Driver Patch S, Naveen B
2004-09-10 14:02 ` Keiichiro Tokunaga
[not found] ` <20040910230200.73eb0374.tokunaga.keiich-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2004-09-16 10:47 ` [PATCH] /sys/firmware/acpi/memory/ for showing info of ACPI memory object Keiichiro Tokunaga
[not found] ` <20040916194725.562b50f0.tokunaga.keiich-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2004-09-24 8:46 ` Keiichiro Tokunaga
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=1095357311.5380.253.camel@localhost \
--to=haveblue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lhms-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=matthew.e.tolentino-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=naveen.b.s-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tokunaga.keiich-+CUm20s59erQFUHtdCDX3A@public.gmane.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