From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Andrea Merello <andrea.merello@iit.it>,
Jagath Jog J <jagathjog1996@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] iio: Add some kerneldoc for channel types
Date: Fri, 24 Feb 2023 16:44:48 +0200 [thread overview]
Message-ID: <d6a6097b-cc48-4213-a5bf-7b154870ce0b@gmail.com> (raw)
In-Reply-To: <CAHp75VdAmUhhP0NF19wOFGGc-v0SWSecywdd5=cBhzbCsSn3BA@mail.gmail.com>
On 2/24/23 16:20, Andy Shevchenko wrote:
> On Fri, Feb 24, 2023 at 3:02 PM Matti Vaittinen
> <mazziesaccount@gmail.com> wrote:
>>
>> For occasional contributor like me navigating the IIO channel types and
>> modifiers may be a daunting task. One may have hard time finding out
>> what type of channel should be used for device data and what units the
>> data should be converted.
>>
>> There is a great documentation for the sysfs interfaces though. What is
>> missing is mapping of the channel types and modifiers to the sysfs
>> documentation (and entries in documentation).
>>
>> Give a hand to a driver writer by providing some documentation and by
>> pointing to the sysfs document from the kerneldocs of respective enums.
>
> kernel doc
>
> Documentation is always welcome!
>
> ...
>
Thanks for the review Andy. All comments valid and to the point - I'll
fix these issues before respinning!
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-02-24 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 13:02 Matti Vaittinen
2023-02-24 14:20 ` Andy Shevchenko
2023-02-24 14:44 ` Matti Vaittinen [this message]
2023-02-24 14:36 ` Jonathan Cameron
2023-02-24 17:16 ` Jonathan Cameron
2023-02-25 7:56 ` Vaittinen, Matti
2023-02-26 17:20 ` 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=d6a6097b-cc48-4213-a5bf-7b154870ce0b@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 \
/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®