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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A4382C433F5 for ; Wed, 4 May 2022 21:19:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231470AbiEDVWy (ORCPT ); Wed, 4 May 2022 17:22:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36308 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229576AbiEDVWi (ORCPT ); Wed, 4 May 2022 17:22:38 -0400 Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 400F351E48 for ; Wed, 4 May 2022 14:18:59 -0700 (PDT) Received: by mail-yb1-xb31.google.com with SMTP id y76so4590489ybe.1 for ; Wed, 04 May 2022 14:18:59 -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=6bErpLDN6CEEoWSzxhVYEvy5hGMXbYXtcuwfFFGVAPk=; b=sWL0jayo/BfRe3n+jU/541fJTcBDKRz3K3MBqQOBfVFyUp3lXVtijyDPbGwHYO9VVN Y7UVxdogikdk6NI+5DxCaqQLBng9/sh7yXAG6TTlEgHVftOtxRnqs5FKRin60E6MUXE1 0jBv8iPox4obg8v1FulX+HmQOlgvhMlC2KKM78UZLu0VIhybG3qNG6oDTXrIThDy7MHe NQLjlQKUEY+lWo1sjIrZyvYvn/yO55hj1PmOUXZU9ffk2LCYOFJhb6TQ9W4X8P4594+9 //eI8vN7+IjAguBRByZZIdQQ6x+CVTCZkwDnQXPKEjeTn1C736aqZXckpAnFre9qwByV XTQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6bErpLDN6CEEoWSzxhVYEvy5hGMXbYXtcuwfFFGVAPk=; b=y9A2klPbXR0J1hKPszqZs2gX0SKazEOZCRTMkKhz1eEFxDnY7qD4zsbSckLl+tpGFF lNpe5B1LYP+2j/GtzsIr9nS2Lv4aygyiST9jAahzTF7o9djUIHV41If+pKW0NsDB+Zoa ysiP7vPozyY6PiuEm3IqM2kFTi0Rd2tLmGvqey6wyXYyPneVlNjGvzdwh48YXX0OEMgZ hJM1aC3WwoYX2R5wCXRIglsz7SOZZoiitCMsNfZ4yGpOeaqDGzMiEIyDkR81OaDY9nxY Af9w1bWPH5b1+L8mz3nN/TdeDzOFX5RuJablMVYUTlADU/KC/qriQ+cmORyz81n8oxxY E5Qg== X-Gm-Message-State: AOAM533yMEKS3ctaCaVIc/oy1l7GhS5bkU3tFSKtDzdRREkm4eHRGr1O JfMdD+IkDMdNLToPy9NL0Wlw5TlPwBtvXjgIUB1PWA== X-Google-Smtp-Source: ABdhPJzz+s6AELg+oOJUfJgzIhMlw+qtR1aNwDxIJCIHUMQYEN1ETifkaKkBhr0GUTxTIHvNmBQAt9dhJ2lpCPMTVc8= X-Received: by 2002:a25:bcc7:0:b0:648:d728:d39 with SMTP id l7-20020a25bcc7000000b00648d7280d39mr19531071ybm.514.1651699138505; Wed, 04 May 2022 14:18:58 -0700 (PDT) MIME-Version: 1.0 References: <20220502164557.3cbb18ca@canb.auug.org.au> In-Reply-To: From: Linus Walleij Date: Wed, 4 May 2022 23:18:47 +0200 Message-ID: Subject: Re: linux-next: manual merge of the pinctrl tree with the gpio-intel tree To: Andy Shevchenko Cc: Stephen Rothwell , Andy Shevchenko , Fabien Dessenne , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Mon, May 2, 2022 at 5:43 PM Andy Shevchenko wrote: > Thanks for the fix. I think the best course of action is that Linus W. > can pull the same branch that GPIO tree has into the pin control tree > and resolve that, because the drivers touched are all pin control > drivers while the core part of GPIO subsystem was updated. Yup did this! Yours, Linus Walleij