From: Sekhar Nori <nsekhar@ti.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: Prabhakar Lad <prabhakar.csengg@gmail.com>,
<davinci-linux-open-source@linux.davincidsp.com>,
<linux-kernel@vger.kernel.org>, <mchehab@infradead.org>,
<linux-media@vger.kernel.org>
Subject: Re: [RESEND-PATCH] media:davinci: clk - {prepare/unprepare} for common clk
Date: Sat, 27 Oct 2012 14:14:27 +0530 [thread overview]
Message-ID: <508B9EEB.2070806@ti.com> (raw)
In-Reply-To: <508AB1D2.40908@ti.com>
Hi Murali,
On 10/26/2012 9:22 PM, Murali Karicheri wrote:
> On 10/25/2012 09:12 AM, Prabhakar Lad wrote:
>> Hi Murali,
>>
>> Thanks for the patch. I'll queue this patch for 3.8.
> Please check with Sekhar as well. This is a preparation patch for common
> clk framework support. ALso fixes some bugs on the existing code. As the
> clk
> patches are dependent on these patches, I would suggest you queue this
> against 3.7 rcx.
The -rc cycle is for fixes only so this cannot get merged into v3.7
as-is. If the patch has some fixes embedded, its a good idea to separate
them out (and have the feature parts come after the fixes in the patch
series) so they can be considered for -rc cycle. The current description
does not detail what the issue is and what its impact is so when you do
separate it out, please mention those as well. It will help determine
the severity of the issue and convince maintainers to include it in v3.7.
Thanks,
Sekhar
next prev parent reply other threads:[~2012-10-27 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 15:36 [RESEND-PATCH] media:davinci: clk - {prepare/unprepare} for common clk Murali Karicheri
2012-10-25 13:12 ` Prabhakar Lad
2012-10-26 15:46 ` Murali Karicheri
2012-10-26 15:52 ` Murali Karicheri
2012-10-27 8:44 ` Sekhar Nori [this message]
2012-10-27 9:59 ` Prabhakar Lad
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 15:50 Murali Karicheri
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=508B9EEB.2070806@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mchehab@infradead.org \
--cc=prabhakar.csengg@gmail.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).