From: Andi Shyti <andi.shyti@samsung.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org, Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH] Documentation: clk: update file names containing referenced structures
Date: Mon, 18 Apr 2016 10:14:59 +0900 [thread overview]
Message-ID: <20160418011459.GC2261@samsunx.samsung> (raw)
In-Reply-To: <20160415154454.0564b1a0@lwn.net>
> > 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
prev parent reply other threads:[~2016-04-18 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 2:48 Andi Shyti
2016-04-15 21:44 ` Jonathan Corbet
2016-04-18 1:14 ` Andi Shyti [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=20160418011459.GC2261@samsunx.samsung \
--to=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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
all inboxes | Powered by JetHome®