From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Jean-François Lessard" <jefflessard3@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] auxdisplay: linedisp: add num_chars sysfs attribute
Date: Tue, 2 Sep 2025 13:04:34 +0300 [thread overview]
Message-ID: <aLbBMumD9mJK2z5U@smile.fi.intel.com> (raw)
In-Reply-To: <20250901020033.60196-4-jefflessard3@gmail.com>
On Sun, Aug 31, 2025 at 10:00:27PM -0400, Jean-François Lessard wrote:
> Add a read-only 'num_chars' sysfs attribute to report display digit count.
>
> The num_chars attribute provides essential capability information to
> userspace applications that need to know display dimensions before writing
> messages, complementing the existing message and scroll controls.
...
> &dev_attr_message.attr,
> &dev_attr_scroll_step_ms.attr,
> + &dev_attr_num_chars.attr,
> &dev_attr_map_seg7.attr,
> &dev_attr_map_seg14.attr,
It looks like we have two groups of the attributes here, can we keep the upper
one sorted? (Put the new attribute one line above?)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-09-02 10:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 2:00 [PATCH 0/5] auxdisplay: linedisp: support attribute attachment to auxdisplay devices Jean-François Lessard
2025-09-01 2:00 ` [PATCH 1/5] auxdisplay: linedisp: encapsulate container_of usage within to_linedisp Jean-François Lessard
2025-09-01 2:00 ` [PATCH 2/5] auxdisplay: linedisp: display static message when length <= display size Jean-François Lessard
2025-09-02 10:03 ` Andy Shevchenko
2025-09-02 17:12 ` Jean-François Lessard
2025-09-01 2:00 ` [PATCH 3/5] auxdisplay: linedisp: add num_chars sysfs attribute Jean-François Lessard
2025-09-02 10:04 ` Andy Shevchenko [this message]
2025-09-02 17:15 ` Jean-François Lessard
2025-09-01 2:00 ` [PATCH 4/5] auxdisplay: linedisp: support attribute attachment to auxdisplay devices Jean-François Lessard
2025-09-02 10:18 ` Andy Shevchenko
2025-09-02 17:37 ` Jean-François Lessard
2025-09-03 10:18 ` Andy Shevchenko
2025-09-03 11:31 ` Jean-François Lessard
2025-09-01 2:00 ` [PATCH 5/5] docs: ABI: auxdisplay: document linedisp library sysfs attributes Jean-François Lessard
2025-09-02 10:59 ` Andy Shevchenko
2025-09-02 17:42 ` Jean-François Lessard
2025-09-02 11:00 ` [PATCH 0/5] auxdisplay: linedisp: support attribute attachment to auxdisplay devices Andy Shevchenko
2025-09-02 17:44 ` Jean-François Lessard
2025-09-08 18:50 ` Jean-François Lessard
2025-09-09 7:12 ` Geert Uytterhoeven
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=aLbBMumD9mJK2z5U@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jefflessard3@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.