netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: zoltan.kiss@citrix.com
Cc: wei.liu2@citrix.com, Ian.Campbell@citrix.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH net 0/4 v2] xen-netback: Fixing up xenvif_tx_check_gop
Date: Sun, 20 Jul 2014 20:57:11 -0700 (PDT)	[thread overview]
Message-ID: <20140720.205711.829460083215756821.davem@davemloft.net> (raw)
In-Reply-To: <1405706885-16763-1-git-send-email-zoltan.kiss@citrix.com>

From: Zoltan Kiss <zoltan.kiss@citrix.com>
Date: Fri, 18 Jul 2014 19:08:01 +0100

> This series fixes a lot of bugs on the error path around this function, which
> were introduced with my grant mapping series in 3.15. They apply to the latest
> net tree, but probably to net-next as well without any modification.
> I'll post an another series which applies to 3.15 stable, as the problem was
> first discovered there. The only difference is that the "queue" variable name is
> replaced to "vif".
> 
> Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com>
> Reported-by: Armin Zentai <armin.zentai@ezit.hu>

Series applied, thanks.

      parent reply	other threads:[~2014-07-21  3:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 18:08 [PATCH net 0/4 v2] xen-netback: Fixing up xenvif_tx_check_gop Zoltan Kiss
2014-07-18 18:08 ` [PATCH net 1/4 v2] xen-netback: Fix handling frag_list on grant op error path Zoltan Kiss
2014-07-18 18:08 ` [PATCH net 2/4 v2] xen-netback: Fix releasing frag_list skbs in " Zoltan Kiss
2014-07-18 18:08 ` [PATCH net 3/4 v2] xen-netback: Fix releasing header slot on " Zoltan Kiss
2014-07-18 18:08 ` [PATCH net 4/4 v2] xen-netback: Fix pointer incrementation to avoid incorrect logging Zoltan Kiss
2014-07-21  3:57 ` David Miller [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=20140720.205711.829460083215756821.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zoltan.kiss@citrix.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).