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 85869C432C0 for ; Mon, 2 Dec 2019 11:45:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 55557217D7 for ; Mon, 2 Dec 2019 11:45:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="JLrik/Q5" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727426AbfLBLpB (ORCPT ); Mon, 2 Dec 2019 06:45:01 -0500 Received: from mail-lf1-f67.google.com ([209.85.167.67]:37509 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727381AbfLBLpB (ORCPT ); Mon, 2 Dec 2019 06:45:01 -0500 Received: by mail-lf1-f67.google.com with SMTP id b15so3470443lfc.4 for ; Mon, 02 Dec 2019 03:45:00 -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=9dbeOa/yZiXLwAKhqVdLm2n/zVETLaeGOMkXijhyOxI=; b=JLrik/Q57hkA2pLMTsCgFgbbXQCV50ILFodTufcKAu1zVJThyK0XovKHqlm3wjIFXo thgwxcec57cupokH5vqIRP6Afm0WjEpc8qBe4nJwWGCNznGEyDTdlFrWzt3OQTWUtu7B 9ojKBJ/a48Jp/wQ+CQoM8wncSSs9mNnuHZ41QHW7sAbD1bWBUOfgQH8nXdwsrzD82tOh +IJzbYXg/z1w5aY7ZGrLvj9474omGAyq7H6tFWkuH4FUM5PHsVMnE5lVUh/cwKaJl5tf /hhm7GuvMk6MXuDzwMfDqLgev32ArbhFfgAw6Pg0WZ76yLzTdJvlrpcRC1xyT7XWfzk0 QIiA== 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=9dbeOa/yZiXLwAKhqVdLm2n/zVETLaeGOMkXijhyOxI=; b=JvGtEWejb9RoxAgHII0cSx1XXsLlv0ZqX8f6Y1tT68EsVJ/kTM5iQAsFDUDDuppUjU 8Wpbg0NkxhMeSO/fSv+SefwpVExy8eCH6NnaNDK1dP+KqIYh3+Pdji0P8V9Z+cAp8skU zWD5iojdPphVUCLLK4r8qm8ctL7TFYVQdI2WCOvr/WB0dnvnU+KjzTT0vFWVf/aLZ+HS bNDEVx7w8KyIl7pn5Y+04NhzySSKKRlvEN2tNRYRv75W+N2xPOQWqM1N/fgHDsY3AXRw FdQnOGXRpUDjb3DN8yqVoB7OcqRd6aY5Tp5h53nf9+p5N/hQ/g+7vBWEYvW0myPr9bYy 7WKA== X-Gm-Message-State: APjAAAV7/epVJVkE3rezqU0HA5yg07VcjIubn4TfesIqHHDt1G7VfGMc b7P4AlwED8zdKyEUQS3lSS4wdLZiNkI1fFNG3KcKdw== X-Google-Smtp-Source: APXvYqyoHJVudY4Th9gkUkwA7ZvcT7SMc/yaucVRZjkFgzCxhl/qzF5ng9XGEy78xknVHWJ5WXqV+foidMFPzNGJqww= X-Received: by 2002:ac2:4945:: with SMTP id o5mr41600526lfi.93.1575287099487; Mon, 02 Dec 2019 03:44:59 -0800 (PST) MIME-Version: 1.0 References: <20191129172537.31410-1-m.felsch@pengutronix.de> In-Reply-To: <20191129172537.31410-1-m.felsch@pengutronix.de> From: Linus Walleij Date: Mon, 2 Dec 2019 12:44:48 +0100 Message-ID: Subject: Re: [PATCH v3 0/6] DA9062 PMIC features To: Marco Felsch Cc: Support Opensource , Lee Jones , Rob Herring , Bartosz Golaszewski , Joel Stanley , Andrew Jeffery , Liam Girdwood , Mark Brown , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , "open list:GPIO SUBSYSTEM" , linux-aspeed , Linux ARM , Sascha Hauer Content-Type: text/plain; charset="UTF-8" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Fri, Nov 29, 2019 at 6:25 PM Marco Felsch wrote: > this series address all comments made on [1]. Patch "gpio: add support > to get local gpio number" is splitted into: > - "gpio: treewide rename gpio_chip_hwgpio to gpiod_to_offset" > - "gpio: make gpiod_to_offset() available for other users" > Please check the discussion [1] for more information. You need to apply > [2] to test the new features. I am very happy with the shape of patches (1) and (2). I can apply these on an immutable branch and merge into the GPIO tree at v5.5-rc1 and offer to other subsystem maintainers to pull in so they can merge the rest of the patch series on top. Alternatively I can merge all the patches into the GPIO tree. I suppose this is not so much of a MFD business at this point so whatever the regulator maintainer prefers I suppose? Yours, Linus Walleij