public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Brad House <brad_mssw@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.0-test11] agpgart [amd64] fix (off by one)
Date: Sun, 30 Nov 2003 21:30:52 +0000	[thread overview]
Message-ID: <20031130213052.GA10414@redhat.com> (raw)
In-Reply-To: <35356.68.105.173.45.1070219694.squirrel@mail.mainstreetsoftworks.com>

On Sun, Nov 30, 2003 at 02:14:54PM -0500, Brad House wrote:
 > AGPGart would report "Too many northbridges" without this
 > patch. The problem was that 'i' was incremented before being
 > checked against the MAX GARTS, just making the check > instead
 > of == fixes the problems.  Patch here:

Already fixed slightly differently in agpgart bitkeeper tree.
I've been trying to get Linus to take this and a few other
similar bits for a while, but they just haven't been 
important enough I guess, so its probably post 2.6.0 material.

		Dave


      reply	other threads:[~2003-11-30 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 19:14 [PATCH 2.6.0-test11] agpgart [amd64] fix (off by one) Brad House
2003-11-30 21:30 ` Dave Jones [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=20031130213052.GA10414@redhat.com \
    --to=davej@redhat.com \
    --cc=brad_mssw@gentoo.org \
    --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