From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Andrea Merello <andrea.merello@iit.it>,
Jagath Jog J <jagathjog1996@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 1/3] iio: Add some kerneldoc for channel types
Date: Tue, 4 Apr 2023 19:43:48 +0300 [thread overview]
Message-ID: <87594ad8-ae4a-c17a-5614-3b504612e738@gmail.com> (raw)
In-Reply-To: <02d3149a-27a1-ac94-45d7-9e8ca67bc73a@infradead.org>
On 4/4/23 19:33, Randy Dunlap wrote:
> Hi Matti,
>
> On 4/4/23 05:24, Matti Vaittinen wrote:
>> +/**
>> + * iio_chan_type - Type of data transferred via IIO channel.
>
> * enum iio_chan_type - ...
>
> as you did in patch 2/3.
>
>> +/**
>> + * iio_modifier - accurate class for channel data
>
> Ditto here.
Well spotted. Thanks Randy. I'll wait for a lil while if there'll be
some more comments - but I'll fix this in v3.
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2023-04-04 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 12:24 [RESEND PATCH v2 0/3] Improve kernel docs Matti Vaittinen
2023-04-04 12:24 ` [RESEND PATCH v2 1/3] iio: Add some kerneldoc for channel types Matti Vaittinen
2023-04-04 16:33 ` Randy Dunlap
2023-04-04 16:43 ` Matti Vaittinen [this message]
2023-04-04 12:25 ` [RESEND PATCH v2 2/3] iio: add documentation for iio_chan_info_enum Matti Vaittinen
2023-04-04 12:25 ` [RESEND PATCH v2 3/3] doc: Make sysfs-bus-iio doc more exact Matti Vaittinen
2023-04-08 9:49 ` [RESEND PATCH v2 0/3] Improve kernel docs Jonathan Cameron
2023-04-10 10:16 ` Matti Vaittinen
2023-04-10 11:34 ` Jonathan Cameron
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=87594ad8-ae4a-c17a-5614-3b504612e738@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andrea.merello@iit.it \
--cc=andy.shevchenko@gmail.com \
--cc=jagathjog1996@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=rdunlap@infradead.org \
/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®