From: Bjorn Helgaas <helgaas@kernel.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
KY Srinivasan <kys@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Hadden Hoppert <haddenh@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH 0/5] PCI: hv: some minor bug fixes and cleanups
Date: Tue, 6 Sep 2016 12:24:43 -0500 [thread overview]
Message-ID: <20160906172443.GB7554@localhost> (raw)
In-Reply-To: <MWHPR03MB266985BDDEE4EB1A9C481B0DBFEB0@MWHPR03MB2669.namprd03.prod.outlook.com>
On Tue, Aug 23, 2016 at 04:42:41AM +0000, Dexuan Cui wrote:
>
> 1. use zero-length array to make the code more readable.
> 2. remove an unused struct member.
> 3. small error handling improvement to some error cases.
>
> Dexuan Cui (5):
> PCI: hv: use zero-length message in struct pci_packet
> PCI: hv: use pci_function_description[0] in struct definitions
> PCI: hv: remove the unused 'wrk' in struct hv_pcibus_device
> PCI: hv: hv_compose_msi_msg: handle the 'ret' value
> PCI: hv: hv_pci_generic_compl(): handle the error case
>
> drivers/pci/host/pci-hyperv.c | 56 ++++++++++++++++++++++---------------------
> 1 file changed, 29 insertions(+), 27 deletions(-)
Applied with KY's ack to pci/host-hv for v4.9, thanks!
next prev parent reply other threads:[~2016-09-06 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 4:42 [PATCH 0/5] PCI: hv: some minor bug fixes and cleanups Dexuan Cui
2016-09-06 15:40 ` Bjorn Helgaas
2016-09-06 17:06 ` KY Srinivasan
2016-09-06 17:05 ` KY Srinivasan
2016-09-06 17:24 ` Bjorn Helgaas [this message]
2016-09-07 1:56 ` Dexuan Cui
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=20160906172443.GB7554@localhost \
--to=helgaas@kernel.org \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haddenh@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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).