[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=MeLfvM28czSrKpmMxmvbDeHi2rxtm+_FCKV24H9C-RBnA@mail.gmail.com>
Date: Mon, 21 Aug 2023 17:04:00 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Asmaa Mnebhi <asmaa@...dia.com>
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()
On Mon, Aug 21, 2023 at 2:55 PM Asmaa Mnebhi <asmaa@...dia.com> wrote:
>
> > > +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.
>
Linus, are you fine with me taking this patch? It will not break the
build and with you taking the other one, next will be fine too.
Bart
Powered by blists - more mailing lists