From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>, ak@suse.de, lm@bitmover.com
Subject: bitkeeper comments
Date: 01 Sep 2003 00:15:30 -0400 [thread overview]
Message-ID: <1062389729.314.31.camel@cube> (raw)
This just got into BitKeeper, about 10 hours ago:
> [PATCH] x86-64 update
>
> Make everything compile and boot again.
>
> The earlier third party ioport.c changes unfortunately
> didn't even compile, fix that too.
>
> - Update defconfig
> - Some minor cleanup
> - Introduce physid_t for APIC masks (fixes UP kernels)
> - Finish ioport.c merge and fix compilation
Several days ago, I mailed Andi Kleen a build log which
showed that ioport.c builds perfectly well on x86-64.
The whole 2.6.0-test4 kernel does in fact, as downloaded
from kernel.org. Andi Kleen agreed...
...and now this comment gets submitted to Linus, ending
up in BitKeeper. I'd like this changed. I realize that
it may be a rather difficult thing to change at this point,
but it is clearly wrong.
next reply other threads:[~2003-09-01 4:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 4:15 Albert Cahalan [this message]
2003-09-01 14:07 ` bitkeeper comments Larry McVoy
2003-09-01 15:26 ` Albert Cahalan
2003-09-01 15:46 ` Larry McVoy
2003-09-01 15:56 ` Christoph Hellwig
2003-09-01 15:59 ` Larry McVoy
2003-09-01 16:02 ` Christoph Hellwig
2003-09-01 16:11 ` Larry McVoy
2003-09-01 16:22 ` Geert Uytterhoeven
2003-09-01 16:15 ` Andi Kleen
2003-09-01 16:59 ` Linus Torvalds
2003-09-01 17:23 ` Jakob Oestergaard
2003-09-01 17:28 ` Christoph Hellwig
2003-09-01 17:40 ` Larry McVoy
2003-09-01 16:33 ` Alan Cox
2003-09-01 16:36 ` Larry McVoy
2003-09-01 16:59 ` Bug in linux-2.6.0-test4 ? dada1
2003-09-01 18:08 ` bitkeeper comments Albert Cahalan
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=1062389729.314.31.camel@cube \
--to=albert@users.sf.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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;
as well as URLs for NNTP newsgroup(s).