From: "Egger, Christoph" <chegger@amazon.de>
To: Matthew Rushton <mrushton7@yahoo.com>,
"roger.pau@citrix.com" <roger.pau@citrix.com>
Cc: "msw@amazon.com" <msw@amazon.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"david.vrabel@citrix.com" <david.vrabel@citrix.com>,
"aliguori@amazon.com" <aliguori@amazon.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>
Subject: Re: [Xen-devel] [PATCH v2 4/4] xen-blkif: drop struct blkif_request_segment_aligned
Date: Wed, 12 Feb 2014 14:43:23 +0100 [thread overview]
Message-ID: <52FB7A7B.2060102@amazon.de> (raw)
In-Reply-To: <1391744311.40091.YahooMailNeo@web122606.mail.ne1.yahoo.com>
On 07.02.14 04:38, Matthew Rushton wrote:
>> This was wrongly introduced in commit 402b27f9, the only difference
>> between blkif_request_segment_aligned and blkif_request_segment is
>> that the former has a named padding, while both share the same
>> memory layout.
>>
>> Also correct a few minor glitches in the description, including for it
>> to no longer assume PAGE_SIZE == 4096.
>
> Tested-by: Matt Rushton <mrushton@amazon.com>
>
> *Corrected subject line from last email and resent. I tested the set and
> everything looks solid. I also reviewed patch 2 and 3.
>
Tested-by: Christoph Egger <chegger@amazon.de>
Reviewed-by: Christoph Egger <chegger@amazon.de>
Christoph
next prev parent reply other threads:[~2014-02-12 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 3:38 [PATCH v2 4/4] xen-blkif: drop struct blkif_request_segment_aligned Matthew Rushton
2014-02-12 13:43 ` Egger, Christoph [this message]
2014-02-12 13:43 ` Egger, Christoph
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=52FB7A7B.2060102@amazon.de \
--to=chegger@amazon.de \
--cc=Ian.Campbell@citrix.com \
--cc=aliguori@amazon.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrushton7@yahoo.com \
--cc=msw@amazon.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.