From: Jeff Garzik <jgarzik@pobox.com>
To: Dave Jones <davej@redhat.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [bk patches] 2.6.x misc updates
Date: Sun, 28 Sep 2003 13:02:06 -0400 [thread overview]
Message-ID: <3F77140E.2080402@pobox.com> (raw)
In-Reply-To: <20030928164002.GA4931@redhat.com>
Dave Jones wrote:
> On Sun, Sep 28, 2003 at 10:44:28AM -0400, Jeff Garzik wrote:
> >
> > Linus, please do a
> >
> > bk pull bk://kernel.bkbits.net/jgarzik/misc-2.5
> >
> > This will update the following files:
> >
> > * char/agp/amd64-agp: properly suffix 64-bit constants
>
> Please don't touch this. It needs fixing in a different way
> for 32bit.
I don't see how the patch could break anything. It's obviously correct,
even if the overall code isn't great for IA32.
Jeff
next prev parent reply other threads:[~2003-09-28 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 14:44 [bk patches] 2.6.x misc updates Jeff Garzik
2003-09-28 16:40 ` Dave Jones
2003-09-28 17:02 ` Jeff Garzik [this message]
2003-09-28 17:38 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2004-11-13 20:54 [BK PATCHES] " Jeff Garzik
2004-12-27 20:15 Jeff Garzik
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=3F77140E.2080402@pobox.com \
--to=jgarzik@pobox.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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