From: Artem Bityutskiy <dedekind1@gmail.com>
To: Neal B <nealb001@gmail.com>
Cc: Artem.Bityutskiy@nokia.com, maximlevitsky@gmail.com,
cascardo@holoscopio.com, linux-kernel@vger.kernel.org,
Julia Lawall <julia@diku.dk>,
linux-mtd@lists.infradead.org, jkosina@suse.cz,
mohanlaljangir@gmail.com, rmk+kernel@arm.linux.org.uk,
dwmw2@infradead.org
Subject: Re: [PATCH 1/6] Mtd: fixed coding style indent errors
Date: Sun, 18 Jul 2010 10:27:26 +0300 [thread overview]
Message-ID: <1279438046.16247.22.camel@localhost.localdomain> (raw)
In-Reply-To: <4C3A8220.6040707@gmail.com>
On Sun, 2010-07-11 at 21:46 -0500, Neal B wrote:
> From f4301b9c13f65d173d67759d53acaf3e8d2331c6 Mon Sep 17 00:00:00 2001
> From: Neal Buckendahl <nealb001@gmail.com>
> Date: Sun, 11 Jul 2010 16:58:24 -0500
> Subject: [PATCH 1/6] Mtd: fixed coding style indent errors found by the
> checkpatch.pl tool
> Signed-off-by: Neal Buckendahl <nealb001@gmail.com>
Unfortunately, your patches are line-wrapped. You should send
non-wrapped patches. Use git send-email - it can do the trick (use
--dry-run first, check everything is fine, then send).
Also, int the commit message, it is a bit better to specify which
exactly warning it fixes.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Neal B <nealb001@gmail.com>
Cc: Artem.Bityutskiy@nokia.com, dwmw2@infradead.org,
rmk+kernel@arm.linux.org.uk, cascardo@holoscopio.com,
mohanlaljangir@gmail.com, maximlevitsky@gmail.com,
Julia Lawall <julia@diku.dk>,
jkosina@suse.cz, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] Mtd: fixed coding style indent errors
Date: Sun, 18 Jul 2010 10:27:26 +0300 [thread overview]
Message-ID: <1279438046.16247.22.camel@localhost.localdomain> (raw)
In-Reply-To: <4C3A8220.6040707@gmail.com>
On Sun, 2010-07-11 at 21:46 -0500, Neal B wrote:
> From f4301b9c13f65d173d67759d53acaf3e8d2331c6 Mon Sep 17 00:00:00 2001
> From: Neal Buckendahl <nealb001@gmail.com>
> Date: Sun, 11 Jul 2010 16:58:24 -0500
> Subject: [PATCH 1/6] Mtd: fixed coding style indent errors found by the
> checkpatch.pl tool
> Signed-off-by: Neal Buckendahl <nealb001@gmail.com>
Unfortunately, your patches are line-wrapped. You should send
non-wrapped patches. Use git send-email - it can do the trick (use
--dry-run first, check everything is fine, then send).
Also, int the commit message, it is a bit better to specify which
exactly warning it fixes.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-07-18 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 2:46 [PATCH 1/6] Mtd: fixed coding style indent errors Neal B
2010-07-12 2:46 ` Neal B
2010-07-18 7:27 ` Artem Bityutskiy [this message]
2010-07-18 7:27 ` Artem Bityutskiy
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=1279438046.16247.22.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=cascardo@holoscopio.com \
--cc=dwmw2@infradead.org \
--cc=jkosina@suse.cz \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@gmail.com \
--cc=mohanlaljangir@gmail.com \
--cc=nealb001@gmail.com \
--cc=rmk+kernel@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.