From: ebiederm@xmission.com (Eric W. Biederman)
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: virtualization@lists.osdl.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: The virtuailization patches break Voyager.
Date: Sat, 28 Apr 2007 10:02:37 -0600 [thread overview]
Message-ID: <m1zm4sebc2.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1177775271.3688.30.camel@mulgrave.il.steeleye.com> (James Bottomley's message of "Sat, 28 Apr 2007 10:47:51 -0500")
James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> I got a bit tired of trying to be proactive. The last time was for the
> %gs per cpu thing, which I saw coming. The basic problem is that
> there's no well organised git tree I can pull from and bisect to trace
> problems.
>
> My strategy now is to wait for the merge window to close and then go
> around sweeping up the mess and yelling at the offenders ... it's what
> all the non-x86 architectures do, and it's definitely an easier process.
Reasonable. I think we would have fewer people to yell at if we
restructured things a bit.
The fact that we have prominent people deliberately ignoring voyager
during development I find disturbing.
In this case I just happened to stumble onto the problem while I was
looking at something else, and decided it wasn't worth doing
development on code that was broken to start with.
Eric
next prev parent reply other threads:[~2007-04-28 16:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 6:40 The virtuailization patches break Voyager Eric W. Biederman
2007-04-28 6:59 ` Jeremy Fitzhardinge
2007-04-28 7:25 ` Eric W. Biederman
2007-04-28 7:52 ` Jeremy Fitzhardinge
2007-04-28 8:32 ` Eric W. Biederman
2007-04-28 8:52 ` Jeremy Fitzhardinge
2007-04-28 9:34 ` Andi Kleen
2007-04-28 16:05 ` James Bottomley
2007-04-28 17:15 ` Andi Kleen
2007-04-28 8:42 ` Andi Kleen
2007-04-28 9:13 ` Thomas Gleixner
2007-04-28 9:15 ` Jeremy Fitzhardinge
2007-04-28 9:39 ` Andi Kleen
2007-04-28 9:48 ` Thomas Gleixner
2007-04-28 9:15 ` Eric W. Biederman
2007-04-28 9:37 ` Andi Kleen
2007-04-28 15:24 ` Eric W. Biederman
2007-04-28 16:08 ` James Bottomley
2007-04-28 15:54 ` James Bottomley
2007-04-28 17:15 ` Andi Kleen
2007-04-28 16:40 ` H. Peter Anvin
2007-04-28 17:00 ` Eric W. Biederman
2007-04-28 17:07 ` H. Peter Anvin
2007-04-28 15:47 ` James Bottomley
2007-04-28 16:02 ` Eric W. Biederman [this message]
2007-04-28 16:18 ` Jeremy Fitzhardinge
2007-04-28 16:20 ` James Bottomley
2007-04-28 17:23 ` Andi Kleen
2007-04-28 17:22 ` Andi Kleen
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=m1zm4sebc2.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=virtualization@lists.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).