qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 1/1] etraxfs_dma: Dont forward zero-length payload to clients
Date: Sat, 20 Feb 2016 00:53:17 +0100	[thread overview]
Message-ID: <20160219235317.GA11438@toto> (raw)
In-Reply-To: <1455623612-24398-1-git-send-email-edgar.iglesias@gmail.com>

On Tue, Feb 16, 2016 at 12:53:32PM +0100, Edgar E. Iglesias wrote:
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>

Applied


> 
> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
>  hw/dma/etraxfs_dma.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/hw/dma/etraxfs_dma.c b/hw/dma/etraxfs_dma.c
> index 9cbb165..d5650eb 100644
> --- a/hw/dma/etraxfs_dma.c
> +++ b/hw/dma/etraxfs_dma.c
> @@ -440,13 +440,16 @@ static int channel_out_run(struct fs_dma_ctrl *ctrl, int c)
>  		D(printf("channel %d pushes %x %u bytes eop=%u\n", c,
>  		         saved_data_buf, len, out_eop));
>  
> -		if (ctrl->channels[c].client->client.push)
> -			ctrl->channels[c].client->client.push(
> -				ctrl->channels[c].client->client.opaque,
> -				buf, len, out_eop);
> -		else
> +		if (ctrl->channels[c].client->client.push) {
> +                        if (len > 0) {
> +				ctrl->channels[c].client->client.push(
> +					ctrl->channels[c].client->client.opaque,
> +					buf, len, out_eop);
> +			}
> +		} else {
>  			printf("WARNING: DMA ch%d dataloss,"
>  			       " no attached client.\n", c);
> +		}
>  
>  		saved_data_buf += len;
>  
> -- 
> 1.9.1
> 

      reply	other threads:[~2016-02-19 23:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 11:53 [Qemu-devel] [PATCH v1 1/1] etraxfs_dma: Dont forward zero-length payload to clients Edgar E. Iglesias
2016-02-19 23:53 ` 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=20160219235317.GA11438@toto \
    --to=edgar.iglesias@gmail.com \
    --cc=qemu-devel@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).