[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221004132723.7b4b03ab@canb.auug.org.au>
Date: Tue, 4 Oct 2022 13:27:23 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Helge Deller <deller@....de>, Dave Airlie <airlied@...hat.com>
Cc: DRI <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
ruanjinjie <ruanjinjie@...wei.com>
Subject: linux-next: manual merge of the fbdev tree with the drm tree
Hi all,
Today's linux-next merge of the fbdev tree got a conflict in:
drivers/video/fbdev/tridentfb.c
between commit:
145eed48de27 ("fbdev: Remove conflicting devices on PCI bus")
from the drm tree and commit:
d738bf0123d6 ("fbdev: tridentfb: Fix missing pci_disable_device() in probe and remove")
from the fbdev tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc drivers/video/fbdev/tridentfb.c
index f9c3b1d38fc2,4d08f4489a0a..000000000000
--- a/drivers/video/fbdev/tridentfb.c
+++ b/drivers/video/fbdev/tridentfb.c
@@@ -1471,11 -1465,7 +1466,11 @@@ static int trident_pci_probe(struct pci
int chip_id;
bool found = false;
+ err = aperture_remove_conflicting_pci_devices(dev, "tridentfb");
+ if (err)
+ return err;
+
- err = pci_enable_device(dev);
+ err = pcim_enable_device(dev);
if (err)
return err;
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists