From: Jens Axboe <jens.axboe@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: virtualization@lists.osdl.org,
Andrew Morton <akpm@linux-foundation.org>,
xen-devel@lists.xensource.com, Roel Kluin <roel.kluin@gmail.com>,
jeremy@xensource.com
Subject: Re: [PATCH] xen/blkfront: beyond ARRAY_SIZE of info->shadow
Date: Fri, 22 May 2009 09:16:09 +0200 [thread overview]
Message-ID: <20090522071609.GF11363@kernel.dk> (raw)
In-Reply-To: <4A15A208.5070206@goop.org>
On Thu, May 21 2009, Jeremy Fitzhardinge wrote:
> Roel Kluin wrote:
>> Do not go beyond ARRAY_SIZE of info->shadow
>>
>> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
>>
> Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>
> Jens, can you put this into a next-merge-window branch?
Sure, will do.
--
Jens Axboe
prev parent reply other threads:[~2009-05-22 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 18:43 [PATCH] xen/blkfront: beyond ARRAY_SIZE of info->shadow Roel Kluin
2009-05-21 18:48 ` Jeremy Fitzhardinge
2009-05-22 7:16 ` Jens Axboe [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=20090522071609.GF11363@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.com \
--cc=roel.kluin@gmail.com \
--cc=virtualization@lists.osdl.org \
--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).