Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752915AbbKPWnZ (ORCPT ); Mon, 16 Nov 2015 17:43:25 -0500 Received: from mail-pa0-f52.google.com ([209.85.220.52]:34799 "EHLO mail-pa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751163AbbKPWnY (ORCPT ); Mon, 16 Nov 2015 17:43:24 -0500 Date: Mon, 16 Nov 2015 14:43:21 -0800 From: Brian Norris To: Joe Perches , Andy Whitcroft Cc: linux-kernel@vger.kernel.org Subject: [BUG] checkpatch: false positive for commits with quote characters Message-ID: <20151116224321.GR8456@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1167 Lines: 34 Hi, What is the Blessed (TM) style for referencing commits that have quote characters in their subject line? e.g., this commit: commit 43163022927b6e7d202a7e6f939c3f392465494d Author: Brian Norris Date: Tue May 19 14:38:22 2015 -0700 mtd: m25p80: allow arbitrary OF matching for "jedec,spi-nor" Checkpatch reports false positive errors like this: ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("")' when I try to reference it on this patch: https://lkml.org/lkml/2015/11/16/826 I understand the double quoting is a little nasty to parse, but I think that just means we should relax the regexes in checkpatch.pl. I could try to patch myself, but I figured I'd just follow checkpatch's advice instead: NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. Brian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/