From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
David Vrabel <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Juergen Gross <JGross@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] xen-pciback: clean up read_dev_bar()
Date: Mon, 6 Jun 2016 09:04:57 -0400 [thread overview]
Message-ID: <575574F9.5040004@oracle.com> (raw)
In-Reply-To: <57554C7502000078000F1DF5@prv-mh.provo.novell.com>
On 06/06/2016 04:12 AM, Jan Beulich wrote:
> - drop unused function parameter
> - simplify determination of 64-bit memory resource
> - use const and unsigned
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2016-06-06 13:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 8:08 [PATCH 0/2] xen-pciback: correct and clean up BAR handling Jan Beulich
2016-06-06 8:11 ` [PATCH 1/2] xen-pciback: return proper values during BAR sizing Jan Beulich
2016-06-06 13:03 ` Boris Ostrovsky
2016-06-06 13:03 ` Boris Ostrovsky
2016-06-06 13:51 ` Jan Beulich
2016-06-06 14:28 ` Boris Ostrovsky
2016-06-06 14:28 ` Boris Ostrovsky
2016-06-06 13:51 ` Jan Beulich
2016-06-06 8:11 ` Jan Beulich
2016-06-06 8:12 ` [PATCH 2/2] xen-pciback: clean up read_dev_bar() Jan Beulich
2016-06-06 8:12 ` Jan Beulich
2016-06-06 13:04 ` Boris Ostrovsky [this message]
2016-06-06 13:04 ` Boris Ostrovsky
2016-06-06 8:47 ` [PATCH 3/2] xen-pciback: drop rom_init() Jan Beulich
2016-06-06 8:47 ` Jan Beulich
2016-06-06 13:09 ` Boris Ostrovsky
2016-06-06 13:09 ` Boris Ostrovsky
2016-06-06 13:54 ` Jan Beulich
2016-06-06 13:54 ` Jan Beulich
2016-06-06 14:35 ` Boris Ostrovsky
2016-06-06 14:35 ` Boris Ostrovsky
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=575574F9.5040004@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.