From: Mike Turquette <mturquette@linaro•org>
To: Kumar Gala <galak@kernel•crashing.org>,
Cc: Yuantian.Tang@freescale•com, devicetree-discuss@lists•ozlabs.org,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] clk/mpc85xx: Update the compatible string
Date: Thu, 30 May 2013 12:44:51 -0700 [thread overview]
Message-ID: <20130530194451.4470.55599@quantum> (raw)
In-Reply-To: <17C23704-7017-427C-A00F-CEFA6247D65D@kernel.crashing.org>
Quoting Kumar Gala (2013-05-30 12:26:38)
> On May 30, 2013, at 2:21 PM, Mike Turquette wrote:
> =
> > Quoting Mike Turquette (2013-05-30 11:57:32)
> >> Quoting Yuantian.Tang@freescale•com (2013-05-22 01:22:19)
> >>> From: Tang Yuantian <yuantian.tang@freescale•com>
> >>> =
> >>> 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@freescale•com>
> >> =
> >> 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 the=
re and shouldn't wait til v3.11
> =
clk-ppc-corenet.c is first introduced in the current clk-next branch.
It is not merged into Linus' tree yet.
Regards,
Mike
> - k
prev parent reply other threads:[~2013-05-30 19:45 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
2013-05-30 18:57 ` Mike Turquette
2013-05-30 19:21 ` Mike Turquette
2013-05-30 19:26 ` Kumar Gala
2013-05-30 19:44 ` Mike Turquette [this message]
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=20130530194451.4470.55599@quantum \
--to=mturquette@linaro$(echo .)org \
--cc=Yuantian.Tang@freescale$(echo .)com \
--cc=devicetree-discuss@lists$(echo .)ozlabs.org \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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