From: Mason <slash.tmp@free.fr>
To: Guenter Roeck <linux@roeck-us.net>, Wim Van Sebroeck <wim@iguana.be>
Cc: Mans Rullgard <mans@mansr.com>, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] watchdog: tango: rename ARCH_TANGOX to ARCH_TANGO
Date: Tue, 19 Jan 2016 11:32:56 +0100 [thread overview]
Message-ID: <569E10D8.2000509@free.fr> (raw)
In-Reply-To: <569D4ACF.6020701@roeck-us.net>
On 18/01/2016 21:27, Guenter Roeck wrote:
> On 01/18/2016 11:50 AM, Mason wrote:
>
>> Requested by arm-soc maintainer Kevin Hilman in v9 review.
>> http://article.gmane.org/gmane.linux.ports.arm.kernel/456331
>
> The reference should be after the '---' (it doesn't explain
> the changes, but provides a reference to the change request),
> and the explanation should be what you have after '---' below,
> ie that the architecture is tango, that the 'x' is a wildcard,
> and that it therefore makes more sense to use ARCH_TANGO
> instead of ARCH_TANGOX.
Hello Guenter,
Thanks for the review.
For the commit message, I am just following Michael's advice:
(one of the clk maintainers)
"Just a single line explaining that the change was requested by the
arm-soc devs in the commit log is helpful. I typically reference these
discussions in the commit log with a link"
Note, I submitted the same patch to clk.
http://article.gmane.org/gmane.linux.kernel.clk/3164
I'd rather have the same commit message for all these trivial fixups.
>> Can this fix be pushed into 4.5 ?
>
> Depends. Is the definition of ARCH_TANGO going to make it in ?
Indeed.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/arch/arm/mach-tango/Kconfig
Regards.
next prev parent reply other threads:[~2016-01-19 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 19:50 [PATCH] watchdog: tango: rename ARCH_TANGOX to ARCH_TANGO Mason
2016-01-18 20:27 ` Guenter Roeck
2016-01-19 10:32 ` Mason [this message]
2016-01-19 12:15 ` Mason
2016-01-19 12:35 ` Måns Rullgård
2016-01-19 13:08 ` Guenter Roeck
2016-01-19 13:18 ` Guenter Roeck
2016-01-21 14:36 ` Mason
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=569E10D8.2000509@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mans@mansr.com \
--cc=wim@iguana.be \
/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