From: harry <harry@hebutterworth.freeserve.co.uk>
To: Daniel Hulme <dh286@cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: sharing PCI devices ....
Date: Wed, 07 Sep 2005 15:16:26 +0100 [thread overview]
Message-ID: <1126102586.3061.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20050907150526.56db42e2@dh286.pem.cam.ac.uk>
On Wed, 2005-09-07 at 15:05 +0100, Daniel Hulme wrote:
> > Also, other people may spot unnoticed bugs in your driver, before they
> > bite you on the bum.
> Actually, on reflection I would like to emphasize that it is the bugs
> that will be biting you on the bum, not the other people. I hope nobody
> else had a horrible mental picture of Xen developers lining up to tell
> some poor chap his code is buggy and then bite him on the bum.
That thought hadn't occurred to me... until now.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-09-07 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 13:42 sharing PCI devices Himanshu Raj
2005-09-07 13:55 ` Daniel Hulme
2005-09-07 14:05 ` Daniel Hulme
2005-09-07 14:16 ` harry [this message]
2005-09-07 15:13 ` Mark Williamson
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=1126102586.3061.0.camel@localhost.localdomain \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=dh286@cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.