public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: brgl@bgdev.pl
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	linus.walleij@linaro.org, andy@kernel.org
Subject: Re: [PATCH] gpio: uapi: clarify default_values being logical
Date: Thu, 15 Feb 2024 09:07:33 +0800	[thread overview]
Message-ID: <20240215010733.GA30995@rigel> (raw)
In-Reply-To: <20240211101421.166779-1-warthog618@gmail.com>

On Sun, Feb 11, 2024 at 06:14:21PM +0800, Kent Gibson wrote:
> The documentation for default_values mentions high/low which can be
> confusing, particularly when the ACTIVE_LOW flag is set.
>
> Replace high/low with active/inactive to clarify that the values are
> logical not physical.
>
> Similarly, clarify the interpretation of values in struct gpiohandle_data.
>
> Signed-off-by: Kent Gibson <warthog618@gmail.com>

Just checking where we are at with this patch, given you've merged the
two documentation patches that followed on from it.

I realize you have bigger fish to fry at the moment, so sorry for any
distraction, but I just want to ensure there isn't something you are
expecting from me or it hasn't fallen through the cracks.

Cheers,
Kent.

  parent reply	other threads:[~2024-02-15  1:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 10:14 [PATCH] gpio: uapi: clarify default_values being logical Kent Gibson
2024-02-11 16:58 ` Andy Shevchenko
2024-02-11 23:13   ` Kent Gibson
2024-02-12  9:28     ` Andy Shevchenko
2024-02-12  9:44       ` Andy Shevchenko
2024-02-12  9:56         ` Kent Gibson
2024-02-13 10:34           ` Kent Gibson
2024-02-13 10:58             ` Andy Shevchenko
2024-02-13 21:36 ` Linus Walleij
2024-02-15  1:07 ` Kent Gibson [this message]
2024-02-15  7:46   ` Bartosz Golaszewski

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=20240215010733.GA30995@rigel \
    --to=warthog618@gmail.com \
    --cc=andy@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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