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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 3E747C5DF60 for ; Tue, 5 Nov 2019 15:05:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1272E21D7C for ; Tue, 5 Nov 2019 15:05:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Kpd/leYt" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731113AbfKEPFU (ORCPT ); Tue, 5 Nov 2019 10:05:20 -0500 Received: from mail-lj1-f196.google.com ([209.85.208.196]:42354 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731109AbfKEPFU (ORCPT ); Tue, 5 Nov 2019 10:05:20 -0500 Received: by mail-lj1-f196.google.com with SMTP id n5so11215985ljc.9 for ; Tue, 05 Nov 2019 07:05:19 -0800 (PST) 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=tavTtm1Xo4MtMh/aOcywS9fElRJcgy1KkS7iJZf+I0o=; b=Kpd/leYtPpqiEDbCJj18CuAu27YXg/BuaSVf6IXKy+NrpoBVTZePZog5GdYjJO9OIi lm4PNz+RaMr2Nrhy8ku0aUXAC05hBbP1JME/FecqDMlBqkYlECiTGsIez1dWe0BBadLu LIVKVjgIW0dw84EB2IjEb0twsx3ASPulZkaAWUIj7h8A2FrFsvuaKTSpTx53DmZ3nq1U QNl8wl6y+nYyPwwlsv+q+D2D2+kZtdPPBtrFK7uj0fyltIejYU1J9AlQptT6e9xIT+GN cLdhsevHXm//qojXfBav6e4dmTJYwtN6Khfo7QLgxUZWvK7zFuFqhWgAr3N+IqYgTJYh VR7Q== 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=tavTtm1Xo4MtMh/aOcywS9fElRJcgy1KkS7iJZf+I0o=; b=M+cAtUbO6366qMoEck/0kswfM4HxRSwZxMiqj6ETzM6d7BazVgum/3T+G+qXkfTvR0 1JWyGOzZORavxgacH6p2VAREf3t+WQDpxhToRuoxiUjj4rcdaUGzrhpuy/bZ3HQEDfXm qvaLXGU1NVeCuBT0F9LrIq71TJGybi6jJ367Og2PtEpC5Zmo+jmwCaWkY/YFqlt8Rhu1 mjxFXgRarSc1TBZbh+dO7EW+EW+jz6E01PQPg9wS0lWOkFikC4IsLlSP9LGD1e7EzjeB aGFJU3EodnnTqVAvvb751ckEsF+cboT+o5ztxDWFsIU1CYZfVacw6qEeuht1OF4O6trz 8WfA== X-Gm-Message-State: APjAAAXIyCVtdR/OO1yidBDwagGulhSmNBZPlFla2fLysYk59RSCYgpX xW1nzNpkHVVStcqRX6xUQIXd0bULPpzIODMsZHTBBA== X-Google-Smtp-Source: APXvYqzg3Toe5ibsBNy4vSKkIj+jEh4yXX7QFUnejT5ioVLHdggVbJujZP6cuxOj2IbLJbzwc/uzWBBvO38pMmBvRbs= X-Received: by 2002:a05:651c:1202:: with SMTP id i2mr23543161lja.218.1572966318371; Tue, 05 Nov 2019 07:05:18 -0800 (PST) MIME-Version: 1.0 References: <411ac5e107cd2a6c628d1fb46e7d284c8f594768.camel@fi.rohmeurope.com> In-Reply-To: <411ac5e107cd2a6c628d1fb46e7d284c8f594768.camel@fi.rohmeurope.com> From: Linus Walleij Date: Tue, 5 Nov 2019 16:05:05 +0100 Message-ID: Subject: Re: [RFC PATCH v3 14/15] gpio: Add definition for GPIO direction To: "Vaittinen, Matti" Cc: "linux-leds@vger.kernel.org" , "dmurphy@ti.com" , "linux-rtc@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "alexandre.belloni@bootlin.com" , "linux-kernel@vger.kernel.org" , "mturquette@baylibre.com" , "lgirdwood@gmail.com" , "devicetree@vger.kernel.org" , "mazziesaccount@gmail.com" , "a.zummo@towertech.it" , "jacek.anaszewski@gmail.com" , "mark.rutland@arm.com" , "robh+dt@kernel.org" , "bgolaszewski@baylibre.com" , "linux-clk@vger.kernel.org" , "sboyd@kernel.org" , "lee.jones@linaro.org" , "broonie@kernel.org" , "pavel@ucw.cz" Content-Type: text/plain; charset="UTF-8" Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org On Mon, Nov 4, 2019 at 4:48 PM Vaittinen, Matti wrote: > > Good initiative (and I will see a ton of janitorial patches as a > > result of this...) > > I have somewhere near 62 patches waiting to be sent =) They're pretty > small but I'd appreciate thorough review as they're mostly untested... > Do you mind receiving them all in one go? Or do you think I should send > the series in smaller chuncks? I would be fine with one patch introducing the defines and then one big patch switching everybody and their dog over to using these definitions. I usually keep to a patch being "one technical step" and it is clearly (IMO) one step to introduce the defines and one step to make use of it in all legacy drivers. It's late in the kernel cycle but this particular part (the defines and switching over old driver to use it) I'd be happy to merge for v5.5. Yours, Linus Walleij