From: harry <harry@hebutterworth.freeserve.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH][7/17] USB virt 2.6 split driver---gnttab channel
Date: Mon, 21 Nov 2005 15:18:55 +0000 [thread overview]
Message-ID: <1132586335.31295.148.camel@localhost.localdomain> (raw)
In-Reply-To: <1132579139.31295.118.camel@localhost.localdomain>
On Mon, 2005-11-21 at 13:18 +0000, harry wrote:
> This patch implements the xenidc_channel interface using grant tables
> but leaves the channel bring-up and tear-down sequencing to a derived
> class (xenidc_gnttab_channel implements that). This code is part of the
> implementation of the xenidc_endpoint used for interdomain communication
> by the USB driver.
The comment above should read:
This patch implements the xenidc_channel interface using grant tables
but leaves the channel bring-up and tear-down sequencing to a derived
class (xenidc_xbgt_channel implements that). This code is part of the
implementation of the xenidc_endpoint used for interdomain communication
by the USB driver.
Sorry for any confusion.
prev parent reply other threads:[~2005-11-21 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 13:18 [PATCH][7/17] USB virt 2.6 split driver---gnttab channel harry
2005-11-21 15:18 ` harry [this message]
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=1132586335.31295.148.camel@localhost.localdomain \
--to=harry@hebutterworth.freeserve.co.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.