From: ebiederm@xmission.com (Eric W. Biederman)
To: David Miller <davem@davemloft.net>
Cc: rusty@rustcorp.com.au, akpm@linux-foundation.org, ak@suse.de,
chrisw@sous-sol.org, jeremy@goop.org, zach@vmware.com,
torvalds@linux-foundation.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization"
Date: Fri, 04 May 2007 21:14:42 -0600 [thread overview]
Message-ID: <m14pmsneql.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070504.194526.53338219.davem@davemloft.net> (David Miller's message of "Fri, 04 May 2007 19:45:26 -0700 (PDT)")
David Miller <davem@davemloft.net> writes:
> From: Rusty Russell <rusty@rustcorp.com.au>
> Date: Sat, 05 May 2007 11:22:48 +1000
>
>> Hi Eric,
>
> To all of those who don't speak "rusty", "Hi Soandso" means
> "NAK".
The question between Rusty and myself is not if we should remove
that code but when.
If we are going to break an ABI I figure the sooner the better,
and the conversation between Rusty and myself has not been totally
unproductive.
Eric
next prev parent reply other threads:[~2007-05-05 3:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 11:56 [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization" Eric W. Biederman
2007-05-04 12:12 ` Rusty Russell
2007-05-04 14:13 ` Eric W. Biederman
2007-05-04 14:37 ` Rusty Russell
2007-05-04 15:07 ` Eric W. Biederman
2007-05-05 1:22 ` Rusty Russell
2007-05-05 2:45 ` David Miller
2007-05-05 3:14 ` Eric W. Biederman [this message]
2007-05-05 3:50 ` David Miller
2007-05-05 2:53 ` Eric W. Biederman
2007-05-05 3:22 ` Rusty Russell
2007-05-05 11:18 ` [PATCH] lguest: don't use paravirt_probe, it's dying Rusty Russell
2007-05-07 1:53 ` Eric W. Biederman
2007-05-04 15:58 ` [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization" Andrew Morton
2007-05-05 1:55 ` Rusty Russell
2007-05-04 14:59 ` Jeremy Fitzhardinge
2007-05-04 15:20 ` Eric W. Biederman
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=m14pmsneql.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--cc=zach@vmware.com \
/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