public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: andrew.grover@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deal with lack of acpi prt entries gracefully
Date: Thu, 11 Sep 2003 15:04:34 -0700	[thread overview]
Message-ID: <20030911220434.GA28095@sgi.com> (raw)
In-Reply-To: <200309112300.30882.adq_dvb@lidskialf.net>

On Thu, Sep 11, 2003 at 11:00:30PM +0100, Andrew de Quincey wrote:
> > None of the above.  We have our own NUMAlink based interrupt protocol
> > model.
> 
> Oooer! Hmm, the existing code would probably NOT like having _PRT entries for 
> a model it doesn't know about.... you could add support for it fairly easily 
> though I suppose...

Yeah, that's what Andy suggested too.  I guess I have to use one of the
reserved fields and try to get the ACPI spec updated.

Thanks,
Jesse

  reply	other threads:[~2003-09-11 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 20:13 [PATCH] deal with lack of acpi prt entries gracefully Jesse Barnes
2003-09-09 20:43 ` Andrew de Quincey
2003-09-09 21:17   ` Jesse Barnes
2003-09-09 21:38     ` Andrew de Quincey
2003-09-09 22:01       ` Jesse Barnes
2003-09-10 21:30         ` Andrew de Quincey
2003-09-10 21:38           ` Jesse Barnes
2003-09-11 20:40             ` Andrew de Quincey
2003-09-11 20:53               ` Jesse Barnes
2003-09-11 21:13                 ` Andrew de Quincey
2003-09-11 21:20                   ` Jesse Barnes
2003-09-11 22:00                     ` Andrew de Quincey
2003-09-11 22:04                       ` Jesse Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-01  1:22 Brown, Len

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=20030911220434.GA28095@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=adq_dvb@lidskialf.net \
    --cc=andrew.grover@intel.com \
    --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