linux-kernel - Re: [PATCH] clk: Update docs after removal of clk-private.h

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: <20150513194344.GB32166@codeaurora.org>
Date:	Wed, 13 May 2015 12:43:44 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Daniel Thompson <daniel.thompson@...aro.org>
Cc:	Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
	linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
	patches@...aro.org, linaro-kernel@...ts.linaro.org,
	Michael Turquette <mturquette@...aro.org>
Subject: Re: [PATCH] clk: Update docs after removal of clk-private.h

On 05/12, Stephen Boyd wrote:
> On 05/11, Daniel Thompson wrote:
> > Currently Documentation/clk.txt describes an obsolete techinique to
> > statically define struct clk objects.
> > 
> > This capability was removed by b09d6d991025("clk: remove clk-private.h")
> > and is no longer supported. The documentation describing the feature should
> > be removed.
> > 
> > Signed-off-by: Daniel Thompson <daniel.thompson@...aro.org>
> > Cc: Jonathan Corbet <corbet@....net>
> > Cc: Michael Turquette <mturquette@...aro.org>
> > Cc: Stephen Boyd <sboyd@...eaurora.org>
> > ---
> 
> We've typically taken patches to this file so I'll apply this to
> clk-next unless there are any objections.
> 

Applied to clk-next.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
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/