From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Marek Vasut <marex@denx.de>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 3/3] IIO: arm: Add LRADC to i.MX28 dts
Date: Mon, 20 Aug 2012 08:57:11 +0100 [thread overview]
Message-ID: <5031EDD7.1050404@jic23.retrosnub.co.uk> (raw)
In-Reply-To: <20120820075249.GJ24242@S2101-09.ap.freescale.net>
On 20/08/12 08:52, Shawn Guo wrote:
> On Mon, Aug 20, 2012 at 08:29:23AM +0100, Jonathan Cameron wrote:
>> Mostly these prefixes are an excuse for grumpy maintainers to moan
>> at people :)
>
> Yeah, I have to become grumpy when my comment gets ignored and I have
> to make it right (for several times) to avoid my upstream moaning at me.
Not at all. My upstream has never moaned at me about it, but I still
like to moan about it myself ;)
>
> Is it so hard? You are not creating a new subsystem but just patching
> an existing file. A "git log" on the file simply shows you how to do it
>
Indeed. A file listing these would be add just one more piece of largely
pointless horrendous documentation.
Perhaps if Marek feels particularly strongly about this, proposing an
additional line to for the SubmittingPatches document to say get your
title format by looking at the log for what you are patching will do
the job? (I can't immediately spot anything equivalent in there...)
next prev parent reply other threads:[~2012-08-20 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344784918-32352-1-git-send-email-marex@denx.de>
[not found] ` <201208170457.03686.marex@denx.de>
[not found] ` <CAAQ0ZWROobdtFkzn9Sr7v5B29zYTQ5YEUZV59kkNE_yv6qbmgQ@mail.gmail.com>
2012-08-19 15:30 ` [PATCH 3/3] IIO: arm: Add LRADC to i.MX28 dts Marek Vasut
2012-08-20 7:29 ` Jonathan Cameron
2012-08-20 7:52 ` Shawn Guo
2012-08-20 7:57 ` Jonathan Cameron [this message]
2012-08-20 13:41 ` Marek Vasut
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=5031EDD7.1050404@jic23.retrosnub.co.uk \
--to=jic23@jic23.retrosnub.co.uk \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=shawn.guo@linaro.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;
as well as URLs for NNTP newsgroup(s).