Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp684964pxb; Wed, 16 Feb 2022 02:00:04 -0800 (PST) X-Google-Smtp-Source: ABdhPJxxv7hgWE+ZDi9UCc55D0Fxb51+IeSVc7W0CfeWFioT8JkzsuhubUqBzAN3eervriS7TgDx X-Received: by 2002:a62:8c44:0:b0:4c4:8072:e588 with SMTP id m65-20020a628c44000000b004c48072e588mr2284846pfd.11.1645005603815; Wed, 16 Feb 2022 02:00:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645005603; cv=none; d=google.com; s=arc-20160816; b=hBiWpK/3rf+STycKXVPmwjKLQF5zhNFw/3xRvpH0MnkFSqBTvX1/NhPNWduqWjRBDo xFktgTm5rz2hEEoMvDAtSL8Cb92wwmKrViSEHLk5+ApwM7M8RqVrmfDTIrgCEpasnXzC QdjMBLJZmvOQCyJEO4YKbcdvp8CQbp7ZeEbT3rGwSmDbwOM0wF4DRBorUClLmNlMf+P5 dVn+JNgnl1R6nTOpPMtKzuMRbIfqZDUAHsKonVy8rrQemqDvULPY1YtCGwhtITgW9LfN dkrh52Hiog3K1A58UmuGnl4Ou5lsrFOORQwjpUzMAvyf92PYRrQRH57TF7iSQzjLpnc0 o+Ww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=C76jbT5fLtK7mnPN0788Is6uC9EFS638zMWrNg3x0FI=; b=sb7uGNUhiZ8kGnFLA7gUB6Mw3aiR3WHm64X2nfaUUfLMLPACEtjantpvBDvKIP0DbS +rNaQphm++iVXoD9VpertmpFVMjhFtP/veri3wYxaJiGZBR0ppZMtD6a/cG09cH8dwbg aJXNw3LuI+ACWgbIZm61uldHGIbtIrldf8ExFUY24UMCIhupqumzupffMHQC5V3Ubr1e iOmfJTxcDiLTLn1hvPmCYVT8azM0ipuQJ1Asxd0iZxRdw/scf7wKd9zB+WTRV8rtfB7R Deh/WHYq135Co79roFOK2zVWJXCuZg/V6WvPHeCH+Fxb9pjA7PKYFn93OvsZ8awwaQhg ZuPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Q52kIAR+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id x16si37380578pfh.311.2022.02.16.02.00.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Feb 2022 02:00:03 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Q52kIAR+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 8D5B42B6226; Wed, 16 Feb 2022 02:00:01 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232599AbiBPKAI (ORCPT + 99 others); Wed, 16 Feb 2022 05:00:08 -0500 Received: from gmail-smtp-in.l.google.com ([23.128.96.19]:48724 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232406AbiBPKAG (ORCPT ); Wed, 16 Feb 2022 05:00:06 -0500 Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0A7CE2B623B; Wed, 16 Feb 2022 01:59:55 -0800 (PST) Received: by mail-qk1-x731.google.com with SMTP id bs32so1270272qkb.1; Wed, 16 Feb 2022 01:59:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C76jbT5fLtK7mnPN0788Is6uC9EFS638zMWrNg3x0FI=; b=Q52kIAR+jY8bAEZKyyg6SmUHa697hLuCWv4gKQeOjDH6lEf5keypJAgOF2sapK6Uml 0miGCpNomfcuoFzRM2kWQWQcmpRmvQKz4tNywYN7fWHPK78ektKsoP4FtA33y96CcnOR mnYUSgRR65YHIjcCuaKbaasHXnuU6pDCjQkYRQ0evduxJ7MKWClu1ek/o8JNeO4zohcP xHuO6Bm5ylLy2ExAWinVckyHrbke9nMhTwXMUP7G6bLWb3Df1n9i/P1kL4e+pZLA5Odm jGKiW+Gn/wDMa9kQFKppB0xLDNHeJZkKV7P4r2d9NIGsswFfJDMhmjp1M90QVgnFjn8U 1wKA== 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=C76jbT5fLtK7mnPN0788Is6uC9EFS638zMWrNg3x0FI=; b=fB1LlB6SIH+qeg3hAmPy9jIV4ZBOfosyY9SxxR+X13uIHVb4vv3dTR5/yNkYpA6rm6 4ECulLmjx5Bjvkg1Ok5M7+hs6vp3htTst0amflCFXESpWpTnqltmqy3zJGJMlFGERSds CmN1LvoeG5f5JCDXe4OoEVMCP1c8ii2wZHpXxV9hgIlHjtkKgsIiM6ebyF8AsVAW92nC 9JSd+E1z0vo2zBWWtkP4cvYHrj8I0CgbPvwR5w+moh51nIoRuyDWrIio/tZsi68rq9Mv djIYSpkfFcCb0+9UNpyfvxB4djc8GoNVdyFQtW0quseLauxNJ+ysNQNRKKRk0ONsezQF hYoQ== X-Gm-Message-State: AOAM531tJTQggBKUzExD/CmrXdelD8oPhE+XmOD3tjdNQamd4IEmBGsZ t0n468rbdHPAz1D4dXaZcVSGFy/IN3lIpLK2kRU= X-Received: by 2002:a37:af45:0:b0:47c:ddbb:b63b with SMTP id y66-20020a37af45000000b0047cddbbb63bmr874780qke.42.1645005594050; Wed, 16 Feb 2022 01:59:54 -0800 (PST) MIME-Version: 1.0 References: <20220213213935.2c5ef8c2@canb.auug.org.au> In-Reply-To: From: Robert Marko Date: Wed, 16 Feb 2022 10:59:43 +0100 Message-ID: Subject: Re: linux-next: Fixes tag needs some work in the qcom tree To: Bjorn Andersson Cc: Stephen Rothwell , Andy Gross , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 Feb 2022 at 05:50, Bjorn Andersson wrote: > > On Sun 13 Feb 03:52 PST 2022, Robert Marko wrote: > > > On Sun, 13 Feb 2022 at 11:39, Stephen Rothwell wrote: > > > > > > Hi all, > > > > > > In commit > > > > > > bf8f5182b8f5 ("clk: qcom: ipq8074: fix PCI-E clock oops") > > > > > > Fixes tag > > > > > > Fixes: f0cfcf1a ("clk: qcom: ipq8074: Add missing clocks for pcie") > > > > > > has these problem(s): > > > > > > - SHA1 should be at least 12 digits long > > > Can be fixed for the future by setting core.abbrev to 12 (or more) > > > or (for git v2.11 or later) just making sure it is not set (or set to > > > "auto"). > > > > Hi Stephen, > > > > Sorry for the short hash, don't know how this happened. > > Do you want me to send a v3 with the fixed hash? > > > > No need, I could update the commit as is. But given that I would have to > rebase 20 other patches I'm hesitant to fix it. Thanks, I will make sure not for this not to happen again. Regards > > Given that checkpatch catches this issue in commit references in the > message and other issues in Fixes I was expecting it to catch this one > as well... Will make sure to look for this going forward (or perhaps > figure out how to improve checkpatch...) > > Thanks, > Bjorn