From: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
To: skhan@linuxfoundation.org, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, sj@kernel.org, dakr@kernel.org,
mic@digikod.net, masahiroy@kernel.org, corbet@lwn.net,
clemens@ladisch.de
Cc: linux-kernel@vger.kernel.org, akhileshpatilvnit@gmail.com
Subject: [PATCH 0/2] samples: timers: hpet_example: Improve user experience
Date: Sun, 17 Aug 2025 18:53:49 +0530 [thread overview]
Message-ID: <cover.1755436239.git.akhilesh@ee.iitb.ac.in> (raw)
Hi all,
This patch series improves user experience for
samples/timers/hpet_example
PATCH 1/2 --> Add support to print help text if user does not provide
required arguments.
PATCH 2/2 --> add help text in timers Kconfig
Testing:
I have tested the changes on x86 with hpet device as follows.
1. Build the sample program
$ gcc hpet_example.c -o hpet_example
2. Run hpet program with no args
$ ./hpet_example
-hpet: requires command
Format: hpet_example <command> </dev/device_name>
Supported commands:
open-close
info
poll
fasync
Example: $ ./hpet_example info /dev/hpet
3. Run and verify hpet commands on /dev/hpet
$ sudo ./hpet_example info /dev/hpet
-hpet: executing info
hpet_info: hi_irqfreq 0x0 hi_flags 0x10 hi_hpet 0 hi_timer 0
Akhilesh Patil (2):
samples: timers: hpet_example: Improve argument parsing
samples: Kconfig: Add help for CONFIG_SAMPLE_TIMER
samples/Kconfig | 3 +++
samples/timers/hpet_example.c | 11 +++++++++--
2 files changed, 12 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2025-08-17 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 13:23 Akhilesh Patil [this message]
2025-08-17 13:24 ` [PATCH 1/2] samples: timers: hpet_example: Improve argument parsing Akhilesh Patil
2025-08-17 13:24 ` [PATCH 2/2] samples: Kconfig: Add help for CONFIG_SAMPLE_TIMER Akhilesh Patil
2025-09-11 16:17 ` [PATCH 0/2] samples: timers: hpet_example: Improve user experience Akhilesh Patil
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=cover.1755436239.git.akhilesh@ee.iitb.ac.in \
--to=akhilesh@ee.iitb.ac.in \
--cc=akhileshpatilvnit@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clemens@ladisch.de \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
--cc=sj@kernel.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®