From: Mark Brown <broonie@kernel.org>
To: Greg KH <greg@kroah.com>, Danilo Krummrich <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Zhi Wang <zhiw@nvidia.com>
Subject: linux-next: manual merge of the driver-core tree with the drm tree
Date: Mon, 17 Aug 2026 16:57:09 +0100 [thread overview]
Message-ID: <aoMvVQiSv8uzbOLb@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
Hi all,
Today's linux-next merge of the driver-core tree got a conflict in:
rust/helpers/pci.c
between commit:
6afbbc27f582b ("rust: pci: add sriov_get_totalvfs() helper")
from the drm tree and commit:
3b5ea0f078e1b ("rust: pci: expose the allocated interrupt type")
from the driver-core 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.
diff --cc rust/helpers/pci.c
index 4ebf256dff230,23b06becb4489..0000000000000
--- a/rust/helpers/pci.c
+++ b/rust/helpers/pci.c
@@@ -24,14 -24,11 +24,19 @@@ __rust_helper bool rust_helper_dev_is_p
return dev_is_pci(dev);
}
+#ifndef CONFIG_PCI_IOV
+__rust_helper unsigned int
+rust_helper_pci_sriov_get_totalvfs(struct pci_dev *pdev)
+{
+ return pci_sriov_get_totalvfs(pdev);
+}
+#endif
+
+ __rust_helper unsigned int rust_helper_pci_irq_type(struct pci_dev *pdev)
+ {
+ return pci_irq_type(pdev);
+ }
+
#ifndef CONFIG_PCI_MSI
__rust_helper int rust_helper_pci_alloc_irq_vectors(struct pci_dev *dev,
unsigned int min_vecs,
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-08-17 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 15:57 Mark Brown [this message]
2026-08-17 20:40 ` linux-next: manual merge of the driver-core tree with the drm tree Danilo Krummrich
-- strict thread matches above, loose matches on Subject: below --
2022-09-26 21:11 broonie
2014-07-24 5:56 Stephen Rothwell
2014-07-24 6:23 ` Greg KH
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=aoMvVQiSv8uzbOLb@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=zhiw@nvidia.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 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.