From: Tony Lindgren <tony@atomide.com>
To: Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
Cc: Nishanth Menon <nm@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: TI816X: add clock domain support for TI816x
Date: Thu, 3 Oct 2013 11:03:49 -0700 [thread overview]
Message-ID: <20131003180349.GO8949@atomide.com> (raw)
In-Reply-To: <5239D7EA.6090104@skitlab.ru>
* Aida Mynzhasova <aida.mynzhasova@skitlab.ru> [130918 09:50]:
>
> So, is there is somebody who wants to review my changes? :)
Maybe resend with Tero and Paul in Cc so they can coordinate
how it should be handled?
Tony
prev parent reply other threads:[~2013-10-03 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 14:02 [PATCH] ARM: OMAP: TI816X: add clock domain support for TI816x Aida Mynzhasova
2013-09-16 6:49 ` Aida Mynzhasova
2013-09-16 13:14 ` Nishanth Menon
2013-09-18 9:40 ` Aida Mynzhasova
2013-09-18 11:56 ` Nishanth Menon
2013-09-18 16:42 ` Aida Mynzhasova
2013-10-03 18:03 ` Tony Lindgren [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=20131003180349.GO8949@atomide.com \
--to=tony@atomide.com \
--cc=aida.mynzhasova@skitlab.ru \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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).