diff for duplicates of <20190320205233.GE251185@google.com> diff --git a/a/1.txt b/N1/1.txt index c66aa57..24fe54a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ [+cc Jon, Jens, Christoph, Sagi, Linus, linux-nvme from related discussion] [+cc Greg, Oliver, who responded to v2 of this patch] -On Fri, Feb 22, 2019@01:48:06PM -0600, Alexandru Gagniuc wrote: +On Fri, Feb 22, 2019 at 01:48:06PM -0600, Alexandru Gagniuc wrote: > A SURPRISE removal of a hotplug PCIe device, caused by a Link Down > event will execute an orderly removal of the driver, which normally > includes releasing the IRQs with pci_free_irq(_vectors): @@ -27,7 +27,7 @@ On Fri, Feb 22, 2019@01:48:06PM -0600, Alexandru Gagniuc wrote: > race condition when the Link Down event occurs right after the > pci_dev_is_disconnected() check. This is outside the scope of this patch. > -> Signed-off-by: Alexandru Gagniuc <mr.nuke.me at gmail.com> +> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> I had actually applied this to pci/msi with the intent of merging it for v5.1, but by coincidence I noticed [1], where Jon was basically @@ -48,7 +48,7 @@ wrong. Bjorn -[1] https://lore.kernel.org/lkml/20190222010502.2434-1-jonathan.derrick at intel.com/T/#u +[1] https://lore.kernel.org/lkml/20190222010502.2434-1-jonathan.derrick@intel.com/T/#u > --- > Changes since v2: diff --git a/a/content_digest b/N1/content_digest index 0d983f3..16f85aa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,13 +1,30 @@ "ref\020190222194808.15962-1-mr.nuke.me@gmail.com\0" - "From\0helgaas@kernel.org (Bjorn Helgaas)\0" - "Subject\0[PATCH v3] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected\0" + "From\0Bjorn Helgaas <helgaas@kernel.org>\0" + "Subject\0Re: [PATCH v3] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected\0" "Date\0Wed, 20 Mar 2019 15:52:33 -0500\0" + "To\0Alexandru Gagniuc <mr.nuke.me@gmail.com>\0" + "Cc\0austin_bolen@dell.com" + alex_gagniuc@dellteam.com + keith.busch@intel.com + Shyam_Iyer@dell.com + lukas@wunner.de + okaya@kernel.org + linux-pci@vger.kernel.org + linux-kernel@vger.kernel.org + Jon Derrick <jonathan.derrick@intel.com> + Jens Axboe <axboe@fb.com> + Christoph Hellwig <hch@lst.de> + Sagi Grimberg <sagi@grimberg.me> + linux-nvme@lists.infradead.org + Linus Torvalds <torvalds@linux-foundation.org> + Greg Kroah-Hartman <gregkh@linuxfoundation.org> + " Oliver O'Halloran <oohall@gmail.com>\0" "\00:1\0" "b\0" "[+cc Jon, Jens, Christoph, Sagi, Linus, linux-nvme from related discussion]\n" "[+cc Greg, Oliver, who responded to v2 of this patch]\n" "\n" - "On Fri, Feb 22, 2019@01:48:06PM -0600, Alexandru Gagniuc wrote:\n" + "On Fri, Feb 22, 2019 at 01:48:06PM -0600, Alexandru Gagniuc wrote:\n" "> A SURPRISE removal of a hotplug PCIe device, caused by a Link Down\n" "> event will execute an orderly removal of the driver, which normally\n" "> includes releasing the IRQs with pci_free_irq(_vectors):\n" @@ -33,7 +50,7 @@ "> race condition when the Link Down event occurs right after the\n" "> pci_dev_is_disconnected() check. This is outside the scope of this patch.\n" "> \n" - "> Signed-off-by: Alexandru Gagniuc <mr.nuke.me at gmail.com>\n" + "> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>\n" "\n" "I had actually applied this to pci/msi with the intent of merging it\n" "for v5.1, but by coincidence I noticed [1], where Jon was basically\n" @@ -54,7 +71,7 @@ "\n" "Bjorn\n" "\n" - "[1] https://lore.kernel.org/lkml/20190222010502.2434-1-jonathan.derrick at intel.com/T/#u\n" + "[1] https://lore.kernel.org/lkml/20190222010502.2434-1-jonathan.derrick@intel.com/T/#u\n" "\n" "> ---\n" "> Changes since v2:\n" @@ -81,4 +98,4 @@ "> 2.19.2\n" > -de346c93f846533dfb442993195f7f4842a8b747473349432222e449cc32fa26 +bb6fa9ccc45163a14bb741df0a3841e1d97d565c48eb0b38c5c2f34983248a98
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.