From: Joe Perches <joe@perches.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
kbuild-all@01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [drm-intel:drm-intel-fixes 52/52] ERROR: Unrecognized email address: 'stable.]'
Date: Wed, 17 Jul 2013 03:01:38 -0700 [thread overview]
Message-ID: <1374055298.1949.87.camel@joe-AO722> (raw)
In-Reply-To: <CAKMK7uEPs-J+vmbc9rqw1FdV2mWucs1EyBB5NBeuqFZU0zz8Qw@mail.gmail.com>
On Wed, 2013-07-17 at 11:29 +0200, Daniel Vetter wrote:
> On Wed, Jul 17, 2013 at 11:10 AM, Fengguang Wu <fengguang.wu@intel.com> 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)
Don't wrap text to start a line with cc:
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
[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.]
next prev parent reply other threads:[~2013-07-17 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51e63ed0.zKgIdwWoDkYbRWqH%fengguang.wu@intel.com>
[not found] ` <20130717091028.GA31187@localhost>
2013-07-17 9:29 ` Daniel Vetter
2013-07-17 10:01 ` Joe Perches [this message]
2013-07-17 11:24 ` Daniel Vetter
2013-07-18 14:58 ` Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1374055298.1949.87.camel@joe-AO722 \
--to=joe@perches.com \
--cc=daniel.vetter@ffwll.ch \
--cc=fengguang.wu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®