From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>, linux-iio@vger.kernel.org
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH 00/11] buffer.h cleanup and split
Date: Sat, 7 Jan 2017 14:45:32 -0500 [thread overview]
Message-ID: <1e5bc993-b630-8646-dd71-f43c83c2c1d9@kernel.org> (raw)
In-Reply-To: <596ebd84-d281-e8d8-8a7e-b4ee460a4739@metafoo.de>
On 04/01/17 13:41, Lars-Peter Clausen wrote:
> On 01/02/2017 08:28 PM, Jonathan Cameron wrote:
>> This series came out of the mess that became apparant when looking at the
>> autogenerated docs. As we pull the kernel-doc from buffer.h in when
>> describing the API the drivers use to access it we were pulling in a lot
>> of documentation that was irrelevant to that use case.
>>
>> Hence, this series does two things:
>> 1) Splits the buffer.h header into two parts:
>> * buffer.h which just contains the stuff that drivers using buffers need.
>> * buffer_impl.h which just contains the stuff related to the implementation
>> of buffers
>> This makes struct iio_buffer opaque to the drivers (with a few extra
>> access functions and a bit of code reorganization)
>> 2) Takes the documentation of struct iio_buffer inline, allowing fairly
>> sensible use of the private: label within docs rather than our local
>> iio specific tagging of documentation. There is an oddity here in that
>> I have deliberately 'broken' the kernel-doc for elements that are private
>> in order to avoid lots of warnings about excess documentation.
>>
>> Along the way various drivers gained additional includes that should probably
>> have been there in the first place. This was needed to cleanup the includes
>> within the includes. Most drivers did it 'right' anyway so this wasn't too
>> bad.
>>
>> I'll probably follow this up with similar cleanups elsewhere at some point.
>>
>> This was against 4.10-rc1 as that's where I'm working on docs, but should
>> go in reasonably cleanly on iio/togreg or iio/testing.
>
> Looks good. I'm not convinced the split is necessary, but it doesn't hurt
> either. Full series:
Yeah, bit marginal on necessity but will make the docs rather nice when I
(or someone else) gets around to documenting how to write a buffer driver.
In the meantime means a lot of irrelevant stuff goes from the driver api
docs on using a buffer.
>
> Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
>
Thanks,
Series applied to the togreg branch of iio.git which will get pushed out as
testing at somepoint soonish.
Jonathan
prev parent reply other threads:[~2017-01-07 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 19:28 [PATCH 00/11] buffer.h cleanup and split Jonathan Cameron
2017-01-02 19:28 ` [PATCH 01/11] iio:buffer: Stop exporting iio_update_demux Jonathan Cameron
2017-01-02 19:28 ` [PATCH 02/11] iio:buffer.h Reformat structure comments to be inline Jonathan Cameron
2017-01-02 19:28 ` [PATCH 03/11] iio:buffer: Introduced a function to assign the buffer specific attrs Jonathan Cameron
2017-01-02 19:28 ` [PATCH 04/11] iio:buffer: Stop exporting iio_scan_mask_query Jonathan Cameron
2017-01-02 19:28 ` [PATCH 05/11] iio:buffers: Push some docs down into the .c file Jonathan Cameron
2017-01-02 19:28 ` [PATCH 06/11] iio:buffer:iio_push_to_buffers_with_timestamp fix kernel-doc Jonathan Cameron
2017-01-02 19:28 ` [PATCH 07/11] iio:kfifo_buf header include push down Jonathan Cameron
2017-01-07 21:52 ` Jonathan Cameron
2017-01-02 19:28 ` [PATCH 08/11] iio:buffer.h include pushdown into buffer implementations Jonathan Cameron
2017-01-02 19:28 ` [PATCH 09/11] iio:buffer: Push implementation of iio_device_attach_buffer into .c file Jonathan Cameron
2017-01-07 22:00 ` Jonathan Cameron
2017-01-02 19:28 ` [PATCH 10/11] iio:dummy: Stop enabling timestamp by default Jonathan Cameron
2017-01-02 19:28 ` [PATCH 11/11] iio:buffer.h - split into buffer.h and buffer_impl.h Jonathan Cameron
2017-01-04 18:41 ` [PATCH 00/11] buffer.h cleanup and split Lars-Peter Clausen
2017-01-07 19:45 ` Jonathan Cameron [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=1e5bc993-b630-8646-dd71-f43c83c2c1d9@kernel.org \
--to=jic23@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).