linux-kernel - Re: [RESEND-PATCH] media:davinci: clk - {prepare/unprepare} for common clk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+V-a8uLMViQvg8YKR8=m0k8hw885qqqZmF9MRjHd5w2RMjezQ@mail.gmail.com>
Date:	Sat, 27 Oct 2012 15:29:16 +0530
From:	Prabhakar Lad <prabhakar.csengg@...il.com>
To:	Sekhar Nori <nsekhar@...com>
Cc:	Murali Karicheri <m-karicheri2@...com>,
	davinci-linux-open-source@...ux.davincidsp.com,
	linux-kernel@...r.kernel.org, mchehab@...radead.org,
	linux-media@...r.kernel.org
Subject: Re: [RESEND-PATCH] media:davinci: clk - {prepare/unprepare} for
 common clk

Sekhar,

On Sat, Oct 27, 2012 at 2:14 PM, Sekhar Nori <nsekhar@...com> wrote:
> 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.
>
Splitting the patch into fixes + features would make sense, Since the features
patch would again change the same piece of code changed by the fixes patch.
The fixes are not so critical enough so as to go into the rc-cycle. I think
merging in 3.8 would be a good idea.

Regards,
--Prabhakar

> Thanks,
> Sekhar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/