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 2D4C4C433EF for ; Mon, 25 Apr 2022 13:33:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232364AbiDYNgY (ORCPT ); Mon, 25 Apr 2022 09:36:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33168 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242113AbiDYNgX (ORCPT ); Mon, 25 Apr 2022 09:36:23 -0400 Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4C1F31150 for ; Mon, 25 Apr 2022 06:33:19 -0700 (PDT) Received: by mail-yb1-xb2e.google.com with SMTP id r189so27059815ybr.6 for ; Mon, 25 Apr 2022 06:33:19 -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=tnGDk2mXj8ducKZ6TjV0CCxMODc0uQNA4u/k6GAYohE=; b=Ru6CMFDL+759FDN0Z+W8VThj6ZOWjiqunT3Ldu7hr9+T/EwHJ2ill2Bu8QHwYvuSAJ 7dKDDU5+92cjc7riK3wLgypUn1DzhEiOL9atp+b4uHycuIbPimmCeKShAzX3/lEkWClR Dw2NBC/VWTnBFQz+EwaDuGAPMCRx5eDKSvbaXRIiTCMVvdOcx71g4s8y03U9A5Yqfk9a x5hIjscu80Kro5O/30lo0/Sc7GCIThTycK8Ke4jCFwjwWctzEXd4/X3ORRR8i9V61+nl ueObE4uewQRN9FEHR07RR5YAM4Y118mzN8MbKAPq/riqju6hAdF621UPSpiO9WZo8tWU VXLg== 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=tnGDk2mXj8ducKZ6TjV0CCxMODc0uQNA4u/k6GAYohE=; b=SCh1lXRH1JwYrf1Bq1RWUhSmVfOBYtEAtf87qDiirypOEFOgX8r6RFBY296TnZr46Y WSCry2ZrODh7dQQP07iEVsjoL3NtBjRkw5Crec5W25tXnIeY15+VuaJpCKIeW7XD37qt fmBAIccDoue/TuL+nfohfMFIy/bUljffr7O4CFPoWtQE3IjxkzfeZGS9kbBXqW/rWdj8 j4Ysbd8Itv2Up/ABYzd5yaA7xuAJoshGJu/4RShy2wdGkKQMB7DQ1fQKqh05LUnffaS7 drxzuqYu3X9e0Fg4i/BfEdaFQIP3+GN7ehmJKrUbc+PfnkftV25Lkems90bNiS9k+AO0 w3Vw== X-Gm-Message-State: AOAM532HxaRp12LgLoHfXscB/ulK+YA8AgKoKID8A3jGLfulWR0V0TXK C8e4EJECAObSaYgSgQC6K4PA6/uqJ90o5rv6I90OoQ== X-Google-Smtp-Source: ABdhPJxT1xHvYnJnmKXomu4Hq7g2Z8f4tfldPU9/2l3zAc4G9If5Or8Dwfh4kiaoWtqonKY9HjM1w65uQiZFxTj56RY= X-Received: by 2002:a25:aa94:0:b0:648:62f2:ef4e with SMTP id t20-20020a25aa94000000b0064862f2ef4emr4562504ybi.626.1650893598522; Mon, 25 Apr 2022 06:33:18 -0700 (PDT) MIME-Version: 1.0 References: <20220421091055.12d6465c@canb.auug.org.au> In-Reply-To: From: Linus Walleij Date: Mon, 25 Apr 2022 15:33:06 +0200 Message-ID: Subject: Re: linux-next: Fixes tags need some work in the pinctrl tree To: Caleb Connolly Cc: Stephen Rothwell , 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, Apr 25, 2022 at 2:27 PM Caleb Connolly wrote: > The patch shouldn't be backported to stable as it will introduce a bug if ported > without the second patch (and as above, I don't think this series should be > backported at all). Could you let me know how to get this dropped from backporting? If Greg or Sasha etc propose the patch for stable (which will not happen automatically unless you explicitly add Cc: stable@vger.kernel.org) they send out a proposal "I will add this patch to stable", with CC to the author, and then you can say you don't want it backported. Many Fixes:-tagged patches do not get picked up for stable, it is not what the tag means, if you want things to be picked for stable, the rule is Cc: stable@, it's just that sometimes the stable maintainers (and an AI!) pick some Fixes: patches anyways. Yours, Linus Walleij