From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: ABI: use Y consistently as channel number
Date: Thu, 19 Dec 2024 15:29:47 +0000 [thread overview]
Message-ID: <20241219152947.0cd882c0@jic23-huawei> (raw)
In-Reply-To: <20241216-doc-iio-use-voltagey-consistently-v1-1-9e34a72133bc@baylibre.com>
On Mon, 16 Dec 2024 17:29:36 -0600
David Lechner <dlechner@baylibre.com> wrote:
> Change X to Y when referring to channel number in the ABI documentation.
> There were only a few cases using X (and one using Z). By far, most
> documented attributes are using Y for the channel number placeholder.
> For consistency, we should follow the same convention throughout.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
Thanks for tidying this up.
Applied.
prev parent reply other threads:[~2024-12-19 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 23:29 [PATCH] iio: ABI: use Y consistently as channel number David Lechner
2024-12-19 15:29 ` 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=20241219152947.0cd882c0@jic23-huawei \
--to=jic23@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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