On Tue, Jun 30, 2020 at 01:09:17PM -0500, Bjorn Helgaas wrote: > PCI: Replace lkml.org, spinics, gmane with lore.kernel.org > > The lkml.org, spinics.net, and gmane.org archives are not very reliable > and, in some cases, not even easily accessible. Replace links to them with > links to lore.kernel.org, the archives hosted by kernel.org. > > I found the gmane items via the Wayback Machine archive at > https://web.archive.org/. > > Signed-off-by: Bjorn Helgaas <bhelgaas@xxxxxxxxxx> I applied this to pci/misc for v5.9. > diff --git a/Documentation/PCI/pci.rst b/Documentation/PCI/pci.rst > index d2815d735c86..281d8a241eae 100644 > --- a/Documentation/PCI/pci.rst > +++ b/Documentation/PCI/pci.rst > @@ -214,7 +214,7 @@ the PCI device by calling pci_enable_device(). This will: > problem and unlikely to get fixed soon. > > This has been discussed before but not changed as of 2.6.19: > - http://lkml.org/lkml/2006/3/2/194 > + https://lore.kernel.org/r/20060302180025.GC28895@xxxxxxxxxxxxxxxxxxxxxx/ > > > pci_set_master() will enable DMA by setting the bus master bit > diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c > index 54ebbef850be..9d7a43261613 100644 > --- a/drivers/pci/quirks.c > +++ b/drivers/pci/quirks.c > @@ -3549,7 +3549,7 @@ static void quirk_no_bus_reset(struct pci_dev *dev) > * The device will throw a Link Down error on AER-capable systems and > * regardless of AER, config space of the device is never accessible again > * and typically causes the system to hang or reset when access is attempted. > - * http://www.spinics.net/lists/linux-pci/msg34797.html > + * https://lore.kernel.org/r/20140923210318.498dacbd@xxxxxxxxxxxxxx/ > */ > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0030, quirk_no_bus_reset); > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0032, quirk_no_bus_reset); > @@ -4378,9 +4378,9 @@ static int pci_acs_ctrl_enabled(u16 acs_ctrl_req, u16 acs_ctrl_ena) > * redirect (CR) since all transactions are redirected to the upstream > * root complex. > * > - * http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/94086 > - * http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/94102 > - * http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/99402 > + * https://lore.kernel.org/r/201207111426.q6BEQTbh002928@xxxxxxxxxxxxx/ > + * https://lore.kernel.org/r/20120711165854.GM25282@xxxxxxx/ > + * https://lore.kernel.org/r/20121005130857.GX4009@xxxxxxx/ > * > * 1002:4385 SBx00 SMBus Controller > * 1002:439c SB7x0/SB8x0/SB9x0 IDE Controller > diff --git a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c > index d21fa04fa44d..43eda101fcf4 100644 > --- a/drivers/pci/setup-res.c > +++ b/drivers/pci/setup-res.c > @@ -73,7 +73,8 @@ static void pci_std_update_resource(struct pci_dev *dev, int resno) > /* > * Apparently some Matrox devices have ROM BARs that read > * as zero when disabled, so don't update ROM BARs unless > - * they're enabled. See https://lkml.org/lkml/2005/8/30/138. > + * they're enabled. See > + * https://lore.kernel.org/r/43147B3D.1030309@xxxxxxxxxx/ > */ > if (!(res->flags & IORESOURCE_ROM_ENABLE)) > return; > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
