From: Jesse Barnes <jbarnes-UzQTBcouhwxWk0Htik3J/w@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Grover,
Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Bjorn Helgaas <bjorn_helgaas-VXdhtT5mjnY@public.gmane.org>,
"Moore,
Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: #define ACPI_MAX_TABLES 256
Date: Mon, 6 Dec 2004 08:01:18 -0800 [thread overview]
Message-ID: <200412060801.19037.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300229FE09-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Sunday, December 5, 2004 6:37 pm, Brown, Len wrote:
> Okay to reduce ACPI_MAX_TABLES to 64 from 256 for the forseeable future?
>
> also, looks like acpi_sdt_entry[] can be __init since it is referenced
> only by code that is __init.
Both are fine by me.
Thanks,
Jesse
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-06 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 2:37 #define ACPI_MAX_TABLES 256 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300229FE09-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-12-06 16:01 ` Jesse Barnes [this message]
2004-12-06 16:13 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 17:56 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8753-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-10-06 21:34 ` 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=200412060801.19037.jbarnes@engr.sgi.com \
--to=jbarnes-uzqtbcouhwxwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=bjorn_helgaas-VXdhtT5mjnY@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@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