From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40A01C43331 for ; Tue, 31 Mar 2020 14:48:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 075692078B for ; Tue, 31 Mar 2020 14:48:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="gjokG7LF" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730662AbgCaOs2 (ORCPT ); Tue, 31 Mar 2020 10:48:28 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:37721 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730574AbgCaOs1 (ORCPT ); Tue, 31 Mar 2020 10:48:27 -0400 Received: by mail-lj1-f195.google.com with SMTP id r24so22317201ljd.4 for ; Tue, 31 Mar 2020 07:48:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N6Xz4CqYuqIBv2ZebWmCGF5bl8QGzp44TRh0S5GDwVs=; b=gjokG7LFkFY7ioSbmzmzaZTgKbNADr/MY5HmpceKvDgbLDoW0JUH0VKunGcKl6Sf3C MOCa3UQ79cYH22mO37ztuqRRVZXezKtdBJqDrIwHfU7IJTRVuYIUlaKzZ8/+TSX4oXzn aKj7korhPUcnruW1P7AI4Rgev9kHGAMysC/Tw25KLZSPPWwq13aeHfQNpvuFNoGHvafb ZXcN6K3+yR/7Bvxm8jQF4PfpWSgyadyQW7UemRq/7S6TqJRMEkS24Vpd5eTe0ZuMOGUr mRee7Fdfu1YQH9h6oWwMHfDiXJ22bW/p7KH19LNrACVayi6n9CAmwuYf+CUQPjJ9e026 vmeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N6Xz4CqYuqIBv2ZebWmCGF5bl8QGzp44TRh0S5GDwVs=; b=GSO561oN837n0p4oyx4kcqcI79R9xA8/ShXwcab1YPe2dUaWl6/LvQbPed0HhmTm6K t5lurAFY9vaAqOYX1Tz4WRQtt8GamZrODFlI884eGR4A1dF4+Ch4PFNKC/iMaHQnyqnE LZ1bo9xHxx3u4jxo5HLtGc0HpsbM40i0FndmM6t8ivgSYMFzZ1D3gJbY+o9UT3RdqlCb EUyryWUfNJwFjh3JPzXHx3Bm0Jim03ilqNdybTQgaNbKfu/8wELJ7HXlxlO5yBainGAx 4J2DWGS1gSOkUt0ZS5YKuYR+eWNNEMCKKj4a0Do/lqn6JWDb4AOF02msFoYr183TBIT5 CVvw== X-Gm-Message-State: AGi0PubSms7exflp68BlU5nKg3lLU/YWvvu4nIENPdH0HcFXMQyP/own +5OstSS7QHGshivlTBLEv10MzDPW7DdqLy441W+KOQ== X-Google-Smtp-Source: APiQypKJfSEDkSQs+ZMk59JfG3Qiy+6BhF4ZV4C4FTck4vZmijIZ/WNKplsHv+iySVWZwiWndiZ7mZURqug3drdWvhg= X-Received: by 2002:a05:651c:23b:: with SMTP id z27mr2629917ljn.125.1585666104014; Tue, 31 Mar 2020 07:48:24 -0700 (PDT) MIME-Version: 1.0 References: <20200330090257.2332864-1-thierry.reding@gmail.com> In-Reply-To: <20200330090257.2332864-1-thierry.reding@gmail.com> From: Linus Walleij Date: Tue, 31 Mar 2020 16:48:13 +0200 Message-ID: Subject: Re: [PATCH] gpio: Avoid using pin ranges with !PINCTRL To: Thierry Reding Cc: Bartosz Golaszewski , "open list:GPIO SUBSYSTEM" , "linux-kernel@vger.kernel.org" , Stephen Rothwell , kbuild test robot Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 30, 2020 at 11:03 AM Thierry Reding wrote: > From: Thierry Reding > > Do not use the struct gpio_device's .pin_ranges field if the PINCTRL > Kconfig symbol is not selected to avoid build failures. > > Fixes: d2fbe53a806e ("gpio: Support GPIO controllers without pin-ranges") > Reported-by: Stephen Rothwell > Reported-by: kbuild test robot > Signed-off-by: Thierry Reding Patch applied with Geert's tags and fixes. Yours, Linus Walleij