From: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] clk/mpc85xx: Update the compatible string
Date: Thu, 30 May 2013 14:26:38 -0500 [thread overview]
Message-ID: <17C23704-7017-427C-A00F-CEFA6247D65D@kernel.crashing.org> (raw)
In-Reply-To: <20130530192143.4470.23214@quantum>
On May 30, 2013, at 2:21 PM, Mike Turquette wrote:
> Quoting Mike Turquette (2013-05-30 11:57:32)
>> Quoting Yuantian.Tang-KZfg59tc24xl57MIdRCFDg@public.gmane.org (2013-05-22 01:22:19)
>>> From: Tang Yuantian <yuantian.tang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>>>
>>> The compatible string of clock is changed from *-2 to *-2.0
>>> on chassis 2. So updated it accordingly.
>>>
>>> Signed-off-by: Tang Yuantian <Yuantian.Tang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>>
>> Taken into clk-next.
>>
>
> One small nitpick. I updated the $SUBJECT to:
>
> clk: mpc85xx: Update the compatible string
>
> The difference being "clk: mpc85xx:" versus "clk/mpc85xx:". Please use
> the former format in the future.
>
> Thanks,
> Mike
Mike,
If clk-ppc-corenet.c went into v3.10, than I think this fix is needed there and shouldn't wait til v3.11
- k
next prev parent reply other threads:[~2013-05-30 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 8:22 [PATCH] clk/mpc85xx: Update the compatible string Yuantian.Tang-KZfg59tc24xl57MIdRCFDg
2013-05-30 18:57 ` Mike Turquette
2013-05-30 19:21 ` Mike Turquette
2013-05-30 19:26 ` Kumar Gala [this message]
[not found] ` <17C23704-7017-427C-A00F-CEFA6247D65D-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2013-05-30 19:44 ` Mike Turquette
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=17C23704-7017-427C-A00F-CEFA6247D65D@kernel.crashing.org \
--to=galak-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).