From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <JGross@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH v4 0/7] xen-pciback: misc cleanup
Date: Wed, 6 Jul 2016 10:41:03 +0100 [thread overview]
Message-ID: <577CD22F.6000007@citrix.com> (raw)
In-Reply-To: <577CC59602000078000FB7A0@prv-mh.provo.novell.com>
On 06/07/16 07:47, Jan Beulich wrote:
> The first five patches are the result of the requested split of
> "xen-pciback: clean up {bar,rom}_init()", with Boris'es R-b
> dropped despite there not being any functional change (the
> mechanical change appears too significant to retain it). The
> remaining two are a follow-up to the recent "xen/pciback: Fix
> conf_space read/write overlap check." and I hope the folding
> in of the formatting correction of two lines touched anyway is
> going to be acceptable this time.
Applied to for-linus-4.8, thanks.
David
prev parent reply other threads:[~2016-07-06 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 6:47 [PATCH v4 0/7] xen-pciback: misc cleanup Jan Beulich
2016-07-06 6:56 ` [PATCH v4 1/7] xen-pciback: drop unused function parameter of read_dev_bar() Jan Beulich
2016-07-06 6:57 ` [PATCH v4 2/7] xen-pciback: drop rom_init() Jan Beulich
2016-07-06 6:57 ` [PATCH v4 3/7] xen-pciback: fold read_dev_bar() into its now single caller Jan Beulich
2016-07-06 6:58 ` [PATCH v4 4/7] xen-pciback: simplify determination of 64-bit memory resource Jan Beulich
2016-07-06 6:58 ` [PATCH v4 5/7] xen-pciback: use const and unsigned in bar_init() Jan Beulich
2016-07-06 6:59 ` [PATCH v4 6/7] xen-pciback: short-circuit read path used for merging write values Jan Beulich
2016-07-06 7:00 ` [PATCH v4 7/7] xen-pciback: drop superfluous variables Jan Beulich
2016-07-06 9:41 ` David Vrabel [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=577CD22F.6000007@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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).