From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: peter.crosthwaite@xilinx.com
Cc: qemu-devel@nongnu.org, Wendy Liang <jliang@xilinx.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 1/1] xilinx_axidma: Do not set DMA .notify to NULL after notify
Date: Mon, 10 Jun 2013 13:10:29 +0200 [thread overview]
Message-ID: <20130610111028.GC5991@smtp.vpn> (raw)
In-Reply-To: <c09de8a7bc669239a1c2f87594d29076fdb49491.1370573523.git.peter.crosthwaite@xilinx.com>
On Fri, Jun 07, 2013 at 01:05:38PM +1000, peter.crosthwaite@xilinx.com wrote:
> From: Wendy Liang <jliang@xilinx.com>
>
> If a stream notify function is not ready, it may re-populate the notify call-
> back to indicate it should be re-polled later. This break in this usage, as
> immediately following the notify() call, .notify is set to NULL. reverse the
> ordering of the notify call and NULL assignment accordingly.
>
> [PC: Reworked commit message]
>
> Signed-off-by: Wendy Liang <jliang@xilinx.com>
> Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Applied master, thanks Wendy and Peter.
ACK for stable.
Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
> ---
> hw/dma/xilinx_axidma.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/dma/xilinx_axidma.c b/hw/dma/xilinx_axidma.c
> index 3a3ef8a..50054cf 100644
> --- a/hw/dma/xilinx_axidma.c
> +++ b/hw/dma/xilinx_axidma.c
> @@ -514,8 +514,9 @@ static void axidma_write(void *opaque, hwaddr addr,
> break;
> }
> if (sid == 1 && d->notify) {
> - d->notify(d->notify_opaque);
> + StreamCanPushNotifyFn notifytmp = d->notify;
> d->notify = NULL;
> + notifytmp(d->notify_opaque);
> }
> stream_update_irq(s);
> }
> --
> 1.8.3.rc1.44.gb387c77.dirty
>
prev parent reply other threads:[~2013-06-10 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 3:05 [Qemu-devel] [PATCH v1 1/1] xilinx_axidma: Do not set DMA .notify to NULL after notify peter.crosthwaite
2013-06-10 11:10 ` Edgar E. Iglesias [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=20130610111028.GC5991@smtp.vpn \
--to=edgar.iglesias@gmail.com \
--cc=jliang@xilinx.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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 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).