From: Tomasz Figa <t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Sachin Kamat
<sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Mike Turquette
<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kyungmin Park
<kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] clk: exynos: Fix typos in DT bindings documentation
Date: Tue, 26 Nov 2013 13:13:15 +0100 [thread overview]
Message-ID: <1538452.UuDUTCGYER@amdc1227> (raw)
In-Reply-To: <CAK9yfHxL8DnN8BE94-L3_MK+dBO0exEq7YAamXRHQ7Abo3jYyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tuesday 26 of November 2013 11:23:49 Sachin Kamat wrote:
> +CC Mike and removed a few from the list.
>
> Hi Laurent,
>
> On 26 November 2013 05:52, Laurent Pinchart
> <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org> wrote:
> > Hi Sachin,
> >
> > On Monday 18 November 2013 17:17:39 Sachin Kamat wrote:
> >> On 18 November 2013 17:16, Laurent Pinchart wrote:
> >> > s/comptible/compatible/
> >> >
> >> > Signed-off-by: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
> >>
> >> Good catch.
> >>
> >> Reviewed-by: Sachin Kamat <sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> >
> > Have you queued up the patch for v3.14 ?
>
> No, I haven't. This should either go through DT tree or else Tomasz Figa can
> pick this up and send it to Mike as per the new workflow for 3.14.
>
>
Well, since this is purely a fix for the documentation, without any
dependencies on clk tree, I see no reason to send it in any other way than
through DT tree directly.
As for clk-samsung tree, I'm currently in process of preparing a tree on
kernel.org so I should start picking up Samsung clock patches soon.
By the way, the patch adding me to MAINTAINERS file has not been merged
yet. Mike, are there any issues?
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-26 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 11:46 [PATCH] clk: exynos: Fix typos in DT bindings documentation Laurent Pinchart
[not found] ` <1384775172-3373-1-git-send-email-laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2013-11-18 11:47 ` Sachin Kamat
[not found] ` <CAK9yfHzA_0AEK8DkBcWFmCNsZGiHUqThD4cyLPgEYPverOWkYA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-26 0:22 ` Laurent Pinchart
2013-11-26 5:53 ` Sachin Kamat
[not found] ` <CAK9yfHxL8DnN8BE94-L3_MK+dBO0exEq7YAamXRHQ7Abo3jYyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-26 12:13 ` Tomasz Figa [this message]
2013-11-26 15:59 ` Laurent Pinchart
2013-12-03 5:42 ` Rob Herring
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=1538452.UuDUTCGYER@amdc1227 \
--to=t.figa-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=sachin.kamat-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).