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 0C0A5C433EF for ; Mon, 14 Feb 2022 04:50:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240389AbiBNEvD (ORCPT ); Sun, 13 Feb 2022 23:51:03 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:39546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233318AbiBNEvA (ORCPT ); Sun, 13 Feb 2022 23:51:00 -0500 Received: from mail-oo1-xc2f.google.com (mail-oo1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0065E50469 for ; Sun, 13 Feb 2022 20:50:53 -0800 (PST) Received: by mail-oo1-xc2f.google.com with SMTP id u25-20020a4ad0d9000000b002e8d4370689so18046579oor.12 for ; Sun, 13 Feb 2022 20:50:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=TaTdYWET/fokCLmaeP1dJHW40gxHNo7JCgJeplFJ/H8=; b=HvXn+CSm2EmiJQqGqdRgo36YxqZrA6ePy0wNVT+3vO9NkHKRZXB+akHRHGPs8HBNxT Mjt6l8j7U0NszCAfewmO8M7tBQS3wlRegGHS/TIKkGoan2mWPG2JA6coJsWjCik11JVR 8XboZ2y5dzG8o4LHAd706aP+ssmIig02U/zAXjc+xDGcNrJnuiAj9vs7oly4x8P4AxLM XFI49VuGw0hBWYAoA4dncgjhd8ukfNRqptFL9Nujqn+XfZTAgNkW9CEftkDWP82W76mI iHn2B6PA0WA705CNSHdJGmfh8ivqLN5Swnw64fZilBhy9Y6Vi21G9nuJty6SZiU7S2k8 emmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=TaTdYWET/fokCLmaeP1dJHW40gxHNo7JCgJeplFJ/H8=; b=0swc8rHu1+KOder6ER2pRv4LBhBf+kFQyReCDQTOKYARqIHqCXnprn9QjN6Dt4MdwX ll0d9gLPWiYBbxVMr8nCUAwyigrNtnTlN4gTXTmJAX3ZG9oHeXF86A66eEYiSLjC6dih nYAyzS256xwKYb7xY4hXzdN3bHn++QqcoeCyHS/Ygcvuq4hZMzwGbbXpbwZSJfx2jz/q nE8LFQfi+2Wfq49bwz24gZqvx0y83n4XUCeea9+mocyQhzvOQSu6QKGMVj0KCMECQkU4 FiI6IrH/aTHYOox6cXZ2mbVF0ZIIAGka81D1eqYue3VR5RiTrJq7WyxHY/wy76byBzoq adxw== X-Gm-Message-State: AOAM531SnEu/OAWLn9ox71XIZzGn+UJPfsJEa7ROoMG0RQSCYFFTRbgY upQMzI4s9/4YjfaHRlFh4aGCOrC/4hg1MA== X-Google-Smtp-Source: ABdhPJxKqSLNn/LDvyfrBak9e//Hj2O4PRVgkgKxmLSJxXIojdrEZQSeSnMZxnz3dMgSRPjrnmGRKg== X-Received: by 2002:a05:6871:506:: with SMTP id s6mr3286197oal.59.1644814253318; Sun, 13 Feb 2022 20:50:53 -0800 (PST) Received: from ripper ([2600:1700:a0:3dc8:205:1bff:fec0:b9b3]) by smtp.gmail.com with ESMTPSA id u3sm15195388oao.25.2022.02.13.20.50.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 13 Feb 2022 20:50:52 -0800 (PST) Date: Sun, 13 Feb 2022 20:53:04 -0800 From: Bjorn Andersson To: Robert Marko Cc: Stephen Rothwell , Andy Gross , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: Fixes tag needs some work in the qcom tree Message-ID: References: <20220213213935.2c5ef8c2@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. 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