From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] Re: [PATCH] ahci: Fix cpu_physical_memory_unmap() argument ordering
Date: Wed, 26 Jan 2011 13:05:12 +0100 [thread overview]
Message-ID: <4D400DF8.7090209@redhat.com> (raw)
In-Reply-To: <1296037496-15429-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 26.01.2011 11:24, schrieb Stefan Hajnoczi:
> The len and is_write arguments to cpu_physical_memory_unmap() were
> swapped. This patch changes calls to use the correct argument ordering.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2011-01-26 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 10:24 [Qemu-devel] [PATCH] ahci: Fix cpu_physical_memory_unmap() argument ordering Stefan Hajnoczi
2011-01-26 12:05 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-23 8:53 Stefan Hajnoczi
2010-12-23 10:43 ` [Qemu-devel] " Alexander Graf
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=4D400DF8.7090209@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).