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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 8A458C7618B for ; Wed, 24 Jul 2019 05:54:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6C5D5218B0 for ; Wed, 24 Jul 2019 05:54:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725870AbfGXFyW (ORCPT ); Wed, 24 Jul 2019 01:54:22 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:59858 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725909AbfGXFyW (ORCPT ); Wed, 24 Jul 2019 01:54:22 -0400 Received: from pps.filterd (m0098394.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6O5qBgY122264 for ; Wed, 24 Jul 2019 01:54:21 -0400 Received: from e06smtp03.uk.ibm.com (e06smtp03.uk.ibm.com [195.75.94.99]) by mx0a-001b2d01.pphosted.com with ESMTP id 2txe9qxxme-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 24 Jul 2019 01:54:20 -0400 Received: from localhost by e06smtp03.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 24 Jul 2019 06:54:18 +0100 Received: from b06avi18626390.portsmouth.uk.ibm.com (9.149.26.192) by e06smtp03.uk.ibm.com (192.168.101.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 24 Jul 2019 06:54:15 +0100 Received: from d06av21.portsmouth.uk.ibm.com (d06av21.portsmouth.uk.ibm.com [9.149.105.232]) by b06avi18626390.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x6O5rwXq38273368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 24 Jul 2019 05:53:58 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C617252050; Wed, 24 Jul 2019 05:54:13 +0000 (GMT) Received: from osiris (unknown [9.152.212.134]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTPS id 85AAC52052; Wed, 24 Jul 2019 05:54:13 +0000 (GMT) Date: Wed, 24 Jul 2019 07:54:12 +0200 From: Heiko Carstens To: Stephen Rothwell Cc: Vasily Gorbik , Christian Borntraeger , Linux Next Mailing List , Linux Kernel Mailing List , Farhan Ali , Cornelia Huck Subject: Re: linux-next: Fixes tag needs some work in the s390-fixes tree References: <20190724074227.63abe116@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190724074227.63abe116@canb.auug.org.au> X-TM-AS-GCONF: 00 x-cbid: 19072405-0012-0000-0000-000003359E68 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19072405-0013-0000-0000-0000216F30E4 Message-Id: <20190724055412.GB4412@osiris> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-07-24_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=7 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907240067 Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org Hi Stephen, On Wed, Jul 24, 2019 at 07:42:27AM +1000, Stephen Rothwell wrote: > In commit > 8b515be512a2 ("vfio-ccw: Fix memory leak and don't call cp_free in cp_init") > Fixes tag > Fixes: 812271b910 ("s390/cio: Squash cp_free() and cp_unpin_free()") > - SHA1 should be at least 12 digits long > Can be fixed 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"). Yes, I noticed this when merging the vfio tree, but decided to not ask for a rebase to fix this. Are your scripts that do sanity checks available somewhere? I'm wondering since I would also like to do some sanity checks before pushing updates to kernel.org like - has the git author signed off the patch? - has the git committer signed off the patch? - are "fixes" tags sane: does commit exist and is format ok?