From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] agpgart/DRM page_mask
Date: Tue, 12 Mar 2002 03:08:30 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905244@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905236@msgid-missing>
Bjorn> I'd like to propose putting the attached patch into the IA64
Bjorn> tree. The point is to be able to support both 460GX and a
Bjorn> similar HP chipset without having to put kludges in DRM.
Bjorn> Chris Ahna and Jeff Hartmann both seem to be OK with this
Bjorn> approach. It's not really IA64-specific, and I did try to
Bjorn> get it directly into 2.4.x/2.5.x, but there's really no
Bjorn> benefit there without the 460GX GART code. So it makes sense
Bjorn> to me to keep it with the 460GX code, and merge both into the
Bjorn> main tree at the same time. -- Bjorn Helgaas -
Bjorn> bjorn_helgaas@hp.com Linux Systems Operation R&D
Bjorn> Hewlett-Packard
The patch looks good to me and I applied it both on the 2.4 and 2.5
trees. Chris, I assume you'll be working on pushing this into the
official trees?
--david
prev parent reply other threads:[~2002-03-12 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 18:18 [Linux-ia64] [PATCH] agpgart/DRM page_mask Bjorn Helgaas
2002-03-12 3:08 ` David Mosberger [this message]
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=marc-linux-ia64-105590701905244@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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