Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754150Ab3GQLYI (ORCPT ); Wed, 17 Jul 2013 07:24:08 -0400 Received: from mail-ea0-f172.google.com ([209.85.215.172]:57342 "EHLO mail-ea0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752437Ab3GQLYG (ORCPT ); Wed, 17 Jul 2013 07:24:06 -0400 Date: Wed, 17 Jul 2013 13:24:05 +0200 From: Daniel Vetter To: Joe Perches Cc: Daniel Vetter , Fengguang Wu , Konstantin Khlebnikov , kbuild-all@01.org, Linux Kernel Mailing List , intel-gfx Subject: Re: [drm-intel:drm-intel-fixes 52/52] ERROR: Unrecognized email address: 'stable.]' Message-ID: <20130717112405.GB4550@phenom.ffwll.local> Mail-Followup-To: Joe Perches , Fengguang Wu , Konstantin Khlebnikov , kbuild-all@01.org, Linux Kernel Mailing List , intel-gfx References: <51e63ed0.zKgIdwWoDkYbRWqH%fengguang.wu@intel.com> <20130717091028.GA31187@localhost> <1374055298.1949.87.camel@joe-AO722> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1374055298.1949.87.camel@joe-AO722> X-Operating-System: Linux phenom 3.10.0-rc7+ 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: 2328 Lines: 55 On Wed, Jul 17, 2013 at 03:01:38AM -0700, Joe Perches wrote: > On Wed, 2013-07-17 at 11:29 +0200, Daniel Vetter wrote: > > On Wed, Jul 17, 2013 at 11:10 AM, Fengguang Wu wrote: > > > FYI, there are new warnings show up in > > > tree: git://people.freedesktop.org/~danvet/drm-intel.git drm-intel-fixes > > > head: 71e4092e52499ec74bc1dec0f883b15f2c424ec5 > > > commit: 71e4092e52499ec74bc1dec0f883b15f2c424ec5 [52/52] drm/i915: fix long-standing SNB regression in power consumption after resume v2 > > > > > > scripts/checkpatch.pl 0001-drm-i915-fix-long-standing-SNB-regression-in-power-c.patch > > > > > > ERROR: Unrecognized email address: 'stable.]' > > > #41: > > > cc: stable.] > > > > Well, I've added that while applying the patch - I tend to smash > > maintainer notes into the sob section and word-wraping caused the cc: > > stable remark to be parsed. Is there an officially sanctioned way for > > such notes that appeases checkpatch? Adding lkml and checkpatch > > maintainer. > > -Daniel > > (It would have been nice to get the content that failes > instead of having to pull the tree) Oops, sorry. > Don't wrap text to start a line with cc: > > Cc: Chris Wilson > Cc: Jesse Barnes > [danvet: Add note about v1 vs. v2 of this patch and use standard > layout for the commit citation. Also add the tested-bys from v1 and a > cc: stable.] > Cc: stable@vger.kernel.org (Note: tiny conflict due to the addition of > > You could have added something like: > > [danvet: Add note about v1 vs. v2 of this patch and use standard > layout for the commit citation. > Also add the tested-bys from v1 and a cc: stable.] Ok, I'll try to rewrap if the cc: hits the first row next time around - just didn't occur to me that checkpatch would notice and I tend to not re-run checkpatch before pushing when editing a patch a bit. Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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/