From: Dan Carpenter <dan.carpenter@oracle.com>
To: Roman Sommer <roman.sommer@fau.de>
Cc: devel@driverdev.osuosl.org, greybus-dev@lists.linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@i4.cs.fau.de, Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org,
Christian Bewermeyer <christian.bewermeyer@fau.de>
Subject: Re: [PATCH v3] staging: greybus: checkpatch: Change parameter type unsigned to unsigned int
Date: Thu, 12 Jan 2017 10:05:10 +0300 [thread overview]
Message-ID: <20170112070510.GC4239@mwanda> (raw)
In-Reply-To: <1484146835-24025-1-git-send-email-roman.sommer@fau.de>
On Wed, Jan 11, 2017 at 04:00:35PM +0100, Roman Sommer wrote:
> Note that this patch does not fix all checkpatch warnings for the
> affected files.
>
A lot of ways that display git commits put the changelog and the summary
far apart. The changelog is pretty useless by itself in this case.
https://lkml.org/lkml/2017/1/11/308
See how it puts the date in between? marc.info is even worse but google
hasn't indexed it yet and I'm too lazy to look it up. So people read
the summary or the changelog but not necessarily both.
regards,
dan carpenter
next prev parent reply other threads:[~2017-01-12 7:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 16:21 [PATCH] greybus: checkpatch: Change parameter type unsigned to unsigned int Roman Sommer
2017-01-10 16:40 ` Johan Hovold
2017-01-10 17:01 ` roman.sommer
2017-01-11 13:48 ` [PATCH v2] " Roman Sommer
2017-01-11 13:52 ` Johan Hovold
2017-01-11 14:44 ` roman.sommer
2017-01-11 14:47 ` roman.sommer
2017-01-11 15:00 ` [PATCH v3] staging: " Roman Sommer
2017-01-11 15:08 ` Johan Hovold
2017-01-12 4:50 ` [greybus-dev] " Viresh Kumar
2017-01-12 7:05 ` Dan Carpenter [this message]
2017-01-12 8:47 ` Johan Hovold
2017-01-13 20:54 ` [PATCH] staging: greybus: fix checkpatch unsigned warnings Roman Sommer
2017-01-16 9:50 ` Johan Hovold
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=20170112070510.GC4239@mwanda \
--to=dan.carpenter@oracle.com \
--cc=christian.bewermeyer@fau.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.sommer@fau.de \
/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