From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Andrea Merello <andrea.merello@iit.it>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jagath Jog J <jagathjog1996@gmail.com>
Subject: Re: [RESEND PATCH v2 0/3] Improve kernel docs
Date: Mon, 10 Apr 2023 12:34:13 +0100 [thread overview]
Message-ID: <20230410123413.0bbd39d3@jic23-huawei> (raw)
In-Reply-To: <CANhJrGPBdJwaoDFy=Rp38k_uSsZrzzMSSKxswwbur67YGG0ZrQ@mail.gmail.com>
On Mon, 10 Apr 2023 13:16:22 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> la 8. huhtik. 2023 klo 12.34 Jonathan Cameron (jic23@kernel.org) kirjoitti:
> >
> > On Tue, 4 Apr 2023 15:24:15 +0300
> > Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> >
> > > IIO has very nice facilities for efficiently providing data from a
> > > device to user (and probably also vice-versa - but I've not used that
> > > direction). Getting started with IIO may not be so simple though - some
> > > of the concepts like triggers and buffers are quite unique.
> > >
> > > This series tries to make it easier for a newcomer to write his/her first
> > > IIO driver by adding some documentation to used enums. Series does not
> > > provide extensive documentation but just documents those few entries I
> > > have become familiar with - but it still aims to be a starting point for
> > > others to add missing bits and pieces.
> > >
> > > This series is marked as v2 because the patch 1 was previously sent as a
> > > stan-alone RFC to collect the missing channel units. RFC can be seen
> > > here:
> > > https://lore.kernel.org/all/10a855f9adc1d710150b7f647500c3c6a769f9ca.1677243698.git.mazziesaccount@gmail.com/
> > >
> > > Patches 2 and 3 were added as a result of discussion followed by the
> > > RFC.
> >
> > Something odd happened on this resend. Patch 1 didn't make it to me
> > or patchwork. I'll reply to previous posting instead.
> >
>
> It seems checkpatch.pl + some of the patches were only picking the
> huawei.com address. Maybe that is the reason?
Nope. Patchwork gets it straight from the list and b4 gets it it from
lore.kernel.org which is also missing patch 1.
>
> This really was a resend with no changes other than rebasing it -
> hence reviewing the v2 was absolutely fine. Thanks for the review!
> I'll check the suggestions and send v3 later this week.
Great.
I'm behind with a few other discussions including the looking at your
questions around that color sensor you want support. So may be
a while before I circle back round to this anyway!
Jonathan
>
> Yours,
> -- Matti
prev parent reply other threads:[~2023-04-10 11:19 UTC|newest]
Thread overview: 6+ 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: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 [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=20230410123413.0bbd39d3@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andrea.merello@iit.it \
--cc=andy.shevchenko@gmail.com \
--cc=jagathjog1996@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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