From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Matthew Fioravante <matthew.fioravante@jhuapl.edu>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 3/7] vtpm Mini-Os domain: mini-os defines
Date: Wed, 25 Aug 2010 17:39:29 +0200 [thread overview]
Message-ID: <20100825153929.GX5341@const.bordeaux.inria.fr> (raw)
In-Reply-To: <4C753378.9070200@jhuapl.edu>
The principle is probably useful indeed.
Matthew Fioravante, le Wed 25 Aug 2010 11:15:04 -0400, a écrit :
> This patch adds some #defines to mini-os
> NO_BLKFRONT
I tend to frown upon "negative" flags, as they're less readable. I know
that using "positive" will require adding them to all other stubdom
projects, but it's probably still better that way: we'll realize for
instance that pv-grub doesn't actually need pcifront :)
samuel
next prev parent reply other threads:[~2010-08-25 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 15:15 [PATCH 3/7] vtpm Mini-Os domain: mini-os defines Matthew Fioravante
2010-08-25 15:39 ` Samuel Thibault [this message]
2010-08-30 11:42 ` Stefano Stabellini
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=20100825153929.GX5341@const.bordeaux.inria.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=matthew.fioravante@jhuapl.edu \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).