On Mon, Mar 6, 2023 at 11:03 AM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > On Sun, Feb 26, 2023 at 9:53 PM Dario Binacchi > <dario.binacchi@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > Since commit 502df79b860563d7 ("gpiolib: Warn on drivers still using static > > gpiobase allocation"), one or more warnings are printed during boot on > > systems where static allocation of GPIO base is used: > > > > [ 1.611480] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. > > [ 1.622893] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. > > [ 1.633272] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation. > > [ 1.643388] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation. > > [ 1.653474] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation. (...) > Linus, > > I'm afraid we'll need to do something about this warning, because > we're getting the same patch for like 4th time already... OK what about reverting commit 502df79b860563d79143be7a1453c2b3224cd836 "gpiolib: Warn on drivers still using static gpiobase allocation" Until we have less drivers with static allocations? In a way it is good that it is fixed, but it's not good if you get snowed under by patches and discussions about this. Yours, Linus Walleij