Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 079D7C64EC4 for ; Mon, 6 Mar 2023 23:08:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230070AbjCFXIL (ORCPT ); Mon, 6 Mar 2023 18:08:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51144 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229702AbjCFXIJ (ORCPT ); Mon, 6 Mar 2023 18:08:09 -0500 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D9A72C66B for ; Mon, 6 Mar 2023 15:08:07 -0800 (PST) Received: by mail-yb1-xb2a.google.com with SMTP id k23so9817064ybk.13 for ; Mon, 06 Mar 2023 15:08:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678144086; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=xJWNmiAqmMOlquXl+tYVU4J1Zj2biLWfltfnZaEEZEE=; b=SPHrevpiyj2EYs8L5vGjWF9+U1wOVedHn/ohQPSRTRfH2ix0ldVVSmbnyOPTHKK8+D CrmmLmkb+n2Zc0QDeGZn32rnCczFdqNbbbfIaVPMCIU/pBd43/aZHhMQSAs1sHUr688E C0R/jrWgkOvpPY0m+FrzoXt/zaOpdj1eChht/LmHZkmdE51wElVFTqW7TKFqh819kHEH XB72kdy1VE5wBYAnrO5TTXC9WHmWlluXmDqXZI+QKj1rTS8p/ES/df4MBasOj7/lqv2S sB/3D3+k0i5OuFcyFfogr/AwXX1eMJ+c0guST1GFAXT/2NlN+jMfuxIxsBhusq7d7dAu uMdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678144086; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=xJWNmiAqmMOlquXl+tYVU4J1Zj2biLWfltfnZaEEZEE=; b=EujFlkQUmW8LX8CAZ6zvoWJ99vwUq9WNSgicBnU2PuR4KqASYJcWMpSNaqD6A0IGfV EBtR2iY1b0IyFQrAX+aIcSy3n4bGuzptCml3xTHOOIM5I6bEKgd5sOoroh+TLf/N9rTP 7XTfyi86q8BlcKtiEKVpoTiduD7FTn5lz77OsLj7zhpenARCXuzxInFsAWNnNgI8Z0zK nOiBG7whAhIealzrcS9kMmA6YlbZvUcJUmCPNYky0i7urC1Xyvqt2vXykvqEpp3JWz6Y MskvVOuPiNfcqCjOHJh0NqfYhTuKbqByInqryXbSC5xvEXmuZHlPyjiewM3uksYrnuhJ eMQA== X-Gm-Message-State: AO0yUKW6m1bmd4yFjZq1/erWLp1Kg788quTvKjZ+WZhmmV1fnHkFPxBq fJBQyp/nBIkA/7fLZbYvz3Jk2yTXaOSDtQQa8BRq7UwxdVDqfevo8qM= X-Google-Smtp-Source: AK7set/r262v9/zoBcT5r5ZLxxh2LiNIhyA7qgBq09jU2JtYL4H83jbraOkZ49WuZDPD1Lu/NfmrieyzNMUNtjnjHG0= X-Received: by 2002:a25:8b8f:0:b0:906:307b:1449 with SMTP id j15-20020a258b8f000000b00906307b1449mr7385460ybl.5.1678144086697; Mon, 06 Mar 2023 15:08:06 -0800 (PST) MIME-Version: 1.0 References: <20230226205319.1013332-1-dario.binacchi@amarulasolutions.com> In-Reply-To: From: Linus Walleij Date: Tue, 7 Mar 2023 00:07:55 +0100 Message-ID: Subject: Re: [PATCH] gpio: mxc: use dynamic allocation of base To: Bartosz Golaszewski , Christophe Leroy Cc: Dario Binacchi , linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 6, 2023 at 11:03=E2=80=AFAM Bartosz Golaszewski = wrote: > On Sun, Feb 26, 2023 at 9:53=E2=80=AFPM Dario Binacchi > wrote: > > > > Since commit 502df79b860563d7 ("gpiolib: Warn on drivers still using st= atic > > 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 deprec= ated, use dynamic allocation. > > [ 1.622893] gpio gpiochip1: Static allocation of GPIO base is deprec= ated, use dynamic allocation. > > [ 1.633272] gpio gpiochip2: Static allocation of GPIO base is deprec= ated, use dynamic allocation. > > [ 1.643388] gpio gpiochip3: Static allocation of GPIO base is deprec= ated, use dynamic allocation. > > [ 1.653474] gpio gpiochip4: Static allocation of GPIO base is deprec= ated, 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