netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: <linux-kernel@vger.kernel.org>,
	Julien Grall <julien.grall@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	"David Vrabel" <david.vrabel@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	<netdev@vger.kernel.org>
Subject: [PATCH v5 0/3] net/xen: Clean up
Date: Wed, 17 Jun 2015 12:38:20 +0100	[thread overview]
Message-ID: <1434541103-31114-1-git-send-email-julien.grall@citrix.com> (raw)

Hi,

The first 2 patches were originally part of the Xen 64KB series [1]. Although
I think they can go without waiting the rest of the 64KB series.

The third patch has been added in the v4.

Regards,

Cc: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>
Cc: David Vrabel <david.vrabel@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: netdev@vger.kernel.org

[1] http://lkml.org/lkml/2015/5/14/533

Julien Grall (3):
  net/xen-netfront: Correct printf format in xennet_get_responses
  net/xen-netback: Remove unused code in xenvif_rx_action
  net/xen-netback: Don't mix hexa and decimal with 0x in the printf
    format

 drivers/net/xen-netback/netback.c | 19 +++++++------------
 drivers/net/xen-netfront.c        |  2 +-
 2 files changed, 8 insertions(+), 13 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-06-17 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 11:38 Julien Grall [this message]
2015-06-17 11:38 ` [PATCH v5 1/3] net/xen-netfront: Correct printf format in xennet_get_responses Julien Grall
2015-06-17 11:38 ` [PATCH v5 2/3] net/xen-netback: Remove unused code in xenvif_rx_action Julien Grall
2015-06-17 11:38 ` [PATCH v5 3/3] net/xen-netback: Don't mix hexa and decimal with 0x in the printf format Julien Grall

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=1434541103-31114-1-git-send-email-julien.grall@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).