From: Dexuan Cui <decui@microsoft.com> To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Cc: "'bhelgaas@google.com'" <bhelgaas@google.com>, "'linux-pci@vger.kernel.org'" <linux-pci@vger.kernel.org>, KY Srinivasan <kys@microsoft.com>, Stephen Hemminger <sthemmin@microsoft.com>, "'olaf@aepfle.de'" <olaf@aepfle.de>, "'apw@canonical.com'" <apw@canonical.com>, "'jasowang@redhat.com'" <jasowang@redhat.com>, "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>, "'driverdev-devel@linuxdriverproject.org'" <driverdev-devel@linuxdriverproject.org>, Haiyang Zhang <haiyangz@microsoft.com>, "'vkuznets@redhat.com'" <vkuznets@redhat.com>, "'marcelo.cerri@canonical.com'" <marcelo.cerri@canonical.com>, "Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>, "'stable@vger.kernel.org'" <stable@vger.kernel.org>, 'Jack Morgenstein' <jackm@mellanox.com> Subject: RE: [PATCH v3 6/6] PCI: hv: fix 2 hang issues in hv_compose_msi_msg() Date: Wed, 14 Mar 2018 17:17:13 +0000 [thread overview] Message-ID: <KL1P15301MB0006D5A4BD0ED296804637C9BFD10@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM> (raw) In-Reply-To: <20180314115000.GC27868@e107981-ln.cambridge.arm.com> > From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> > Sent: Wednesday, March 14, 2018 04:50 > On Tue, Mar 13, 2018 at 06:23:39PM +0000, Dexuan Cui wrote: > > [...] > > > Hi Lorenzo, Bjorn, and all, > > Do you need more ACKs? Currently Michael and Haiyang reviewed and ack'd > > the patchset. > > > > Should I send a v4 that just removes the "CC: stable@vger.kernel.org" tag > > for patches 1, 2, 4 and 5? I tend to avoid a v4 as I supppose it would be > > easier if you just remove the tags if you belive it's necessary (IMHO all the > > 6 paches are not big and it would be great if we can have all of them in > > the old stable kernels, but I respect your decision). > > I think you need a v4 since for patches that are actually fixing a bug I > want a Fixes: tag added and I want them to be applicable independently > of other patches in the series. Send them in a separate series if you > prefer - I just want to make sure they apply independently. Ok, I'll send 2 series: one for [6/6] PCI: hv: fix 2 hang issues in hv_compose_msi_msg() [3/6] PCI: hv: serialize the present/eject work items These fix real issues reported by Mellanox when they tested SR-IOV with VMs runnning on Hyper-V. I'll add stable tags for them. The other series will cover these 4 patces which don't need to go in stable: [5/6] PCI: hv: hv_pci_devices_present(): only queue a new work when necessary [4/6] PCI: hv: remove hbus->enum_sem [2/6] PCI: hv: hv_eject_device_work(): remove the bogus test [1/6] PCI: hv: fix a comment typo in _hv_pcifront_read_config() > As for marking patches for stable kernels, I do not think it is right > to send cosmetic churn to stable kernels anyway, at least that's my > reading of the policy. > > You can easily post a v4 with patches reshuffled - I will apply them > accordingly. OK. > Before re-posting please read this to improve formatting (I can do it > for you but while at it you can do it yourself): > https://marc.info/?l=linux-pci&m=150905742808166&w=2 Will read. Thanks! -- Dexuan
WARNING: multiple messages have this Message-ID (diff)
From: Dexuan Cui <decui@microsoft.com> To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Cc: "'bhelgaas@google.com'" <bhelgaas@google.com>, "'linux-pci@vger.kernel.org'" <linux-pci@vger.kernel.org>, KY Srinivasan <kys@microsoft.com>, Stephen Hemminger <sthemmin@microsoft.com>, "'olaf@aepfle.de'" <olaf@aepfle.de>, "'apw@canonical.com'" <apw@canonical.com>, "'jasowang@redhat.com'" <jasowang@redhat.com>, "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>, "'driverdev-devel@linuxdriverproject.org'" <driverdev-devel@linuxdriverproject.org>, Haiyang Zhang <haiyangz@microsoft.com>, "'vkuznets@redhat.com'" <vkuznets@redhat.com>, "'marcelo.cerri@canonical.com'" <marcelo.cerri@canonical.com>, "Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>, "'stable@vger.kernel.org'" <stable@vger.kernel.org>, 'Jack Morgenstein' <jackm@mellanox.com> Subject: RE: [PATCH v3 6/6] PCI: hv: fix 2 hang issues in hv_compose_msi_msg() Date: Wed, 14 Mar 2018 17:17:13 +0000 [thread overview] Message-ID: <KL1P15301MB0006D5A4BD0ED296804637C9BFD10@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM> (raw) In-Reply-To: <20180314115000.GC27868@e107981-ln.cambridge.arm.com> > From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> > Sent: Wednesday, March 14, 2018 04:50 > On Tue, Mar 13, 2018 at 06:23:39PM +0000, Dexuan Cui wrote: >=20 > [...] >=20 > > Hi Lorenzo, Bjorn, and all, > > Do you need more ACKs? Currently Michael and Haiyang reviewed and ack'd > > the patchset. > > > > Should I send a v4 that just removes the "CC: stable@vger.kernel.org" t= ag > > for patches 1, 2, 4 and 5? I tend to avoid a v4 as I supppose it would = be > > easier if you just remove the tags if you belive it's necessary (IMHO a= ll the > > 6 paches are not big and it would be great if we can have all of them i= n > > the old stable kernels, but I respect your decision). >=20 > I think you need a v4 since for patches that are actually fixing a bug I > want a Fixes: tag added and I want them to be applicable independently > of other patches in the series. Send them in a separate series if you > prefer - I just want to make sure they apply independently. Ok, I'll send 2 series: one for [6/6] PCI: hv: fix 2 hang issues in hv_compose_msi_msg() [3/6] PCI: hv: serialize the present/eject work items These fix real issues reported by Mellanox when they tested SR-IOV with VMs runnning on Hyper-V. I'll add stable tags for them. The other series will cover these 4 patces which don't need to go in stable= : [5/6] PCI: hv: hv_pci_devices_present(): only queue a new work when necessa= ry [4/6] PCI: hv: remove hbus->enum_sem [2/6] PCI: hv: hv_eject_device_work(): remove the bogus test [1/6] PCI: hv: fix a comment typo in _hv_pcifront_read_config() =20 > As for marking patches for stable kernels, I do not think it is right > to send cosmetic churn to stable kernels anyway, at least that's my > reading of the policy. >=20 > You can easily post a v4 with patches reshuffled - I will apply them > accordingly. OK. =20 > Before re-posting please read this to improve formatting (I can do it > for you but while at it you can do it yourself): > https://marc.info/?l=3Dlinux-pci&m=3D150905742808166&w=3D2 Will read. Thanks! -- Dexuan
next prev parent reply other threads:[~2018-03-14 17:17 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-06 18:21 [PATCH v3 0/6] some fixes to the pci-hyperv driver Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:21 ` [PATCH v3 1/6] PCI: hv: fix a comment typo in _hv_pcifront_read_config() Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-09 19:36 ` Haiyang Zhang 2018-03-09 19:36 ` Haiyang Zhang 2018-03-06 18:21 ` [PATCH v3 2/6] PCI: hv: hv_eject_device_work(): remove the bogus test Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:29 ` Michael Kelley (EOSG) 2018-03-06 18:29 ` Michael Kelley (EOSG) 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-06 18:21 ` [PATCH v3 3/6] PCI: hv: serialize the present/eject work items Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:30 ` Michael Kelley (EOSG) 2018-03-06 18:30 ` Michael Kelley (EOSG) 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-06 18:21 ` [PATCH v3 4/6] PCI: hv: remove hbus->enum_sem Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:31 ` Michael Kelley (EOSG) 2018-03-06 18:31 ` Michael Kelley (EOSG) 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-06 18:21 ` [PATCH v3 5/6] PCI: hv: hv_pci_devices_present(): only queue a new work when necessary Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:31 ` Michael Kelley (EOSG) 2018-03-06 18:31 ` Michael Kelley (EOSG) 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-09 19:37 ` Haiyang Zhang 2018-03-06 18:21 ` [PATCH v3 6/6] PCI: hv: fix 2 hang issues in hv_compose_msi_msg() Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:21 ` Dexuan Cui 2018-03-06 18:32 ` Michael Kelley (EOSG) 2018-03-06 18:32 ` Michael Kelley (EOSG) 2018-03-07 12:34 ` Lorenzo Pieralisi 2018-03-07 21:40 ` Dexuan Cui 2018-03-07 21:40 ` Dexuan Cui 2018-03-13 18:23 ` Dexuan Cui 2018-03-13 18:23 ` Dexuan Cui 2018-03-13 18:31 ` Lorenzo Pieralisi 2018-03-13 18:31 ` Lorenzo Pieralisi 2018-03-13 18:31 ` Lorenzo Pieralisi 2018-03-14 11:50 ` Lorenzo Pieralisi 2018-03-14 11:50 ` Lorenzo Pieralisi 2018-03-14 11:50 ` Lorenzo Pieralisi 2018-03-14 17:17 ` Dexuan Cui [this message] 2018-03-14 17:17 ` Dexuan Cui 2018-03-09 19:38 ` Haiyang Zhang 2018-03-09 19:38 ` Haiyang Zhang 2018-03-09 19:38 ` Haiyang Zhang 2018-03-09 19:38 ` Haiyang Zhang
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=KL1P15301MB0006D5A4BD0ED296804637C9BFD10@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM \ --to=decui@microsoft.com \ --cc=Michael.H.Kelley@microsoft.com \ --cc=apw@canonical.com \ --cc=bhelgaas@google.com \ --cc=driverdev-devel@linuxdriverproject.org \ --cc=haiyangz@microsoft.com \ --cc=jackm@mellanox.com \ --cc=jasowang@redhat.com \ --cc=kys@microsoft.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=marcelo.cerri@canonical.com \ --cc=olaf@aepfle.de \ --cc=stable@vger.kernel.org \ --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: linkBe 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.