linux-kernel - Re: [PATCH] Documentation: clk: update file names containing referenced structures

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: <20160418011459.GC2261@samsunx.samsung>
Date:	Mon, 18 Apr 2016 10:14:59 +0900
From:	Andi Shyti <andi.shyti@...sung.com>
To:	Jonathan Corbet <corbet@....net>
Cc:	linux-doc@...r.kernel.org,
	Michael Turquette <mturquette@...libre.com>,
	linux-kernel@...r.kernel.org, Andi Shyti <andi@...zian.org>
Subject: Re: [PATCH] Documentation: clk: update file names containing
 referenced structures

> > Commit 'b09d6d991' removes include/linux/clk-private.h and
> > re-arranges the clock related structures contained in it in
> > different files. The documentation has not been updated
> > accordingly, thus it wasn't anymore consistent.
> > 
> > Place the structures referenced by Documentation/clk.txt in the
> > correct files and update their contents to the latest status.
> [...]
> >  Below is the common struct clk definition from
> > -include/linux/clk-private.h, modified for brevity:
> > -
> > -	struct clk {
> > -		const char		*name;
> > -		const struct clk_ops	*ops;
> > -		struct clk_hw		*hw;
> > -		char			**parent_names;
> > -		struct clk		**parents;
> > -		struct clk		*parent;
> > -		struct hlist_head	children;
> > -		struct hlist_node	child_node;
> > +include/linux/clk.c, modified for brevity:
> > +
> 
> Um...include/linux/clk.c?  We have 19 files named clk.c, but none of them
> (unsurprisingly) are under include/ .  
> 
> The patch also seems to have a bunch of gratuitous white-space changes?

yes, sorry, I put too little brain when I formatted it and I was 
too fast when I sent it... I will put a little more brain next
time :)

Thanks,
Andi