linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan+linaro@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/3] gpiolib: fix debugfs newline separators
Date: Mon, 28 Oct 2024 13:49:57 +0100	[thread overview]
Message-ID: <20241028125000.24051-1-johan+linaro@kernel.org> (raw)

I've noticed this before on some systems but never got around to looking
into why the gpio debugfs newline separators are sometimes missing.

On recent Qualcomm machines with 10+ gpio chips this can get really
annoying when a third of the separators are missing (e.g. when verifying
pin settings). Hence the CC stable tag.

Johan


Johan Hovold (3):
  gpiolib: fix debugfs newline separators
  gpiolib: fix debugfs dangling chip separator
  gpiolib: clean up debugfs separator handling

 drivers/gpio/gpiolib.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-10-28 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 12:49 Johan Hovold [this message]
2024-10-28 12:49 ` [PATCH 1/3] gpiolib: fix debugfs newline separators Johan Hovold
2024-10-28 12:49 ` [PATCH 2/3] gpiolib: fix debugfs dangling chip separator Johan Hovold
2024-10-31 17:02   ` Bartosz Golaszewski
2024-10-31 17:07     ` Johan Hovold
2024-10-31 18:08       ` Bartosz Golaszewski
2024-10-28 12:50 ` [PATCH 3/3] gpiolib: clean up debugfs separator handling Johan Hovold
2024-10-31 18:15   ` Bartosz Golaszewski
2024-10-31 18:14 ` (subset) [PATCH 0/3] gpiolib: fix debugfs newline separators Bartosz Golaszewski
2024-11-04  7:51 ` 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=20241028125000.24051-1-johan+linaro@kernel.org \
    --to=johan+linaro@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;
as well as URLs for NNTP newsgroup(s).