From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the gpio-brgl tree with the origin tree
Date: Wed, 21 Oct 2026 14:05:53 +0100 [thread overview]
Message-ID: <ati4sVaUOZm_N6pa@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]
Hi all,
Today's linux-next merge of the gpio-brgl tree got a conflict in:
drivers/gpio/gpiolib-kunit.c
between commit:
851bb4a429916 ("gpio: kunit: fix GPIO device reference leak with __free()")
from the origin tree and commit:
c3e8906112e0c ("gpio: kunit: factor out common code for waiting for device probe")
from the gpio-brgl 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 drivers/gpio/gpiolib-kunit.c
index 6a2c8b34f34bb,c5d4637ea2c58..0000000000000
--- a/drivers/gpio/gpiolib-kunit.c
+++ b/drivers/gpio/gpiolib-kunit.c
@@@ -27,9 -29,21 +29,23 @@@
#define GPIO_TEST_PROVIDER_NGPIO 4
+KUNIT_DEFINE_ACTION_WRAPPER(gpio_device_put_wrapper, gpio_device_put, struct gpio_device *);
+
+ static void gpio_test_device_check_bound(struct kunit *test,
+ struct device *dev, bool expected)
+ {
+ bool bound = false;
+
+ wait_for_device_probe();
+ scoped_guard(device, dev)
+ bound = device_is_bound(dev);
+
+ if (expected)
+ KUNIT_ASSERT_TRUE(test, bound);
+ else
+ KUNIT_ASSERT_FALSE(test, bound);
+ }
+
/*
* The test provider tracks per-line direction and value so that lines can be
* driven as both inputs and outputs - this is needed to exercise input as well
@@@ -772,9 -737,7 +739,8 @@@ static void gpio_hog_assert(struct kuni
struct property_entry properties[2];
struct platform_device *pdev;
struct fwnode_handle *fwnode;
+ struct gpio_device *gdev;
struct gpio_desc *desc;
- bool bound = true;
int ret;
fwnode = software_node_fwnode(&gpio_test_provider_swnode);
@@@ -792,12 -755,10 +758,12 @@@
wait_for_device_probe();
/* The hog must have configured the line with the expected direction. */
- gdev = gpio_device_find_by_label(GPIO_CONSUMER_NAME);
- struct gpio_device *gdev __free(gpio_device_put) =
- gpio_device_find_by_label(GPIO_TEST_PROVIDER);
++ gdev = gpio_device_find_by_label(GPIO_TEST_PROVIDER);
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, gdev);
+ ret = kunit_add_action_or_reset(test, gpio_device_put_wrapper, gdev);
+ KUNIT_ASSERT_EQ(test, ret, 0);
+
desc = gpio_device_get_desc(gdev, offset);
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, desc);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-10-21 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 13:05 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-09 14:44 Mark Brown
2026-11-09 14:44 Mark Brown
2026-08-12 16:45 Mark Brown
2026-08-18 7:44 ` Geert Uytterhoeven
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=ati4sVaUOZm_N6pa@sirena.co.uk \
--to=broonie@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®