[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CH2PR12MB38950DCD03CFB45E4DB34E32D71EA@CH2PR12MB3895.namprd12.prod.outlook.com>
Date: Mon, 21 Aug 2023 12:55:25 +0000
From: Asmaa Mnebhi <asmaa@...dia.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
CC: "andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"bgolaszewski@...libre.com" <bgolaszewski@...libre.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v5 2/2] gpio: mlxbf3: Support add_pin_ranges()
> > +MODULE_SOFTDEP("pre: pinctrl-mlxbf3");
> > MODULE_DESCRIPTION("NVIDIA BlueField-3 GPIO Driver");
> > MODULE_AUTHOR("Asmaa Mnebhi <asmaa@...dia.com>");
> > MODULE_LICENSE("Dual BSD/GPL");
> > --
> > 2.30.1
> >
>
> It's not clear to me whether this depends on patch 1? If only at run-time then I
> guess Linus and I can take the two patches through ours respective trees?
Indeed from a build point of view, there is no dependency so you could take the 2 patches through your respective tree. However, at run-time, the gpio-mlxbf3.c driver fails to load without the pinctrl-mlxbf3.c driver. Should I add a "depends on" in the Kconfig? Then you will have to include both patches in your tree.
Thanks.
Asmaa
Powered by blists - more mailing lists