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=-10.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_NONE,URIBL_BLOCKED autolearn=unavailable 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 0B88EC47084 for ; Tue, 25 May 2021 15:09:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D64326141C for ; Tue, 25 May 2021 15:09:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231377AbhEYPKu (ORCPT ); Tue, 25 May 2021 11:10:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56590 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230110AbhEYPKu (ORCPT ); Tue, 25 May 2021 11:10:50 -0400 Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ADAAAC061574 for ; Tue, 25 May 2021 08:09:18 -0700 (PDT) Received: by mail-lj1-x22b.google.com with SMTP id e2so32258961ljk.4 for ; Tue, 25 May 2021 08:09:18 -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=VXhstycvJ/ZxY8r6rEvIPljRylC1sPEk0zKGubyDqnc=; b=BkHE3p4fPN34oOAaNSE02dOwEecfhj/NQtDloDqQc+xn+yc/uj4k7T1GAhnkoP7XK5 PAirC+CqUOlNV4agBX4g9/Ge6HdzmhIku6IGO1lZlAQ4HoUyPFHWGpKqSpYR4oCZ17/x OL4NFaTV9ufHRrTmyXNPQy0SobLF2Ah9Y/tHmZgKuKoywMAr/qH4eq4OhSBPU+fW+iew lDytQ6AVAFVeL5MfFadlSqcfKptxdCKCSmg60GJGHFKBdWVJjN6us/ZAJ3izcjLvMERO yT9gaICJf2Nc/0SKF4R1mlJwpRq4RbvU1REAIzGEeLOMIo34QkHzOBHiHCvo0l+vpuOR E/dQ== 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=VXhstycvJ/ZxY8r6rEvIPljRylC1sPEk0zKGubyDqnc=; b=Hko2bnaHcjS3EhwuOnN3Jf82p2p0YizlqlBhU9HO+OunsOM7ylRGHFhqAiztN+p84R ZqF5VBHqeSk/oRlueQK/Xefm80puR4c6PkJfAjhRhhufevi8OGHEElljXjjOUkfkJzjV 21shTavw2S9FeZ6V52X813ZtFtzAHNdem+QHr8WXa7TckSsYajg5VxPXzaBQpc34jUKn zbKmEkFCDUbUDv5biYX2ghxDLQK6XC0IbDeVcBJyZg9mX/ecb62mLJ0X9RbCsae4bXup Oa+ZxmsYuegIoUa/6OYhA3s+EKTmDgSSwe9Q1gsJ/wq0qWPCfrKLab8z/G7TOkw7S9xL sEnQ== X-Gm-Message-State: AOAM532AXZwC4e9fg0WiWRDaS0EYGLbv/DbOj1c+wizuHrvVUa9sLLDA 05SVGZ6G04ThlriqHfkXzixaWsjLgUimNfqWZGLYNA== X-Google-Smtp-Source: ABdhPJxLgO3lpcEhQzJRZHtjBBS37mdWQMb5YUpDCqSSE+VsKji9pL95xpoUjuJXjYq+UoY6D/AWgxbpMKAO5jVryg0= X-Received: by 2002:a2e:90c7:: with SMTP id o7mr21231147ljg.368.1621955356716; Tue, 25 May 2021 08:09:16 -0700 (PDT) MIME-Version: 1.0 References: <20210512210316.1982416-1-luzmaximilian@gmail.com> In-Reply-To: From: Linus Walleij Date: Tue, 25 May 2021 17:09:05 +0200 Message-ID: Subject: Re: [PATCH] pinctrl/amd: Add device HID for new AMD GPIO controller To: Andy Shevchenko Cc: Maximilian Luz , "open list:GPIO SUBSYSTEM" , linux-kernel , stable , Sachi King Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Thu, May 20, 2021 at 11:09 AM Andy Shevchenko wrote: > On Thu, May 20, 2021 at 01:50:50AM +0200, Linus Walleij wrote: > > On Wed, May 12, 2021 at 11:03 PM Maximilian Luz wrote: > > > > > Add device HID AMDI0031 to the AMD GPIO controller driver match table. > > > This controller can be found on Microsoft Surface Laptop 4 devices and > > > seems similar enough that we can just copy the existing AMDI0030 entry. > > > > > > Cc: # 5.10+ > > > > Why? It's hardly a regression? > > IIRC the stable policy allows to backport new IDs. You're right. > > > Tested-by: Sachi King > > > Signed-off-by: Maximilian Luz > > > > I've applied the patch for next without the stable tag for now. > > It can be pulled to stable afterwards anyway :-) Nah I'll tag it back on. But it goes upstream with the rest of patches for v5.14 in the merge window because it is not urgent. Yours, Linus Walleij