From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yu Chien Peter Lin via buildroot <buildroot@buildroot.org>
Cc: Yu Chien Peter Lin <peterlin@andestech.com>
Subject: Re: [Buildroot] [PATCH] package/kmon: new package
Date: Sun, 14 Jul 2024 18:11:01 +0200 [thread overview]
Message-ID: <20240714181101.20b59529@windsurf> (raw)
In-Reply-To: <20240512074459.1360700-1-peterlin@andestech.com>
Hello!
On Sun, 12 May 2024 15:44:59 +0800
Yu Chien Peter Lin via buildroot <buildroot@buildroot.org> wrote:
> Add Kmon, a Rust-based, text-UI tool for managing Linux kernel
> modules and monitoring kernel activities, providing a single
> interface for various tools like dmesg and kmod.
>
> Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
Thanks a lot for your patch, and sorry for the delay in getting back to
you. I have applied your patch, with some small changes. See below.
> ---
> package/Config.in | 1 +
> package/kmon/Config.in | 9 +++++++++
> package/kmon/kmon.hash | 4 ++++
> package/kmon/kmon.mk | 12 ++++++++++++
> 4 files changed, 26 insertions(+)
An entry in the DEVELOPERS file was missing, so I added it.
> +KMON_VERSION = v1.6.5
> +KMON_SITE = $(call github,orhun,kmon,$(KMON_VERSION))
Here we don't want the "v" in "v1.6.5" to be in the KMON_VERSION, but
in KMON_SITE, so that KMON_VERSION has a chance to match with the
version reported by the release-monitoring.org service.
As said: applied with those 2 (small) changes.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-14 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 7:44 [Buildroot] [PATCH] package/kmon: new package Yu Chien Peter Lin via buildroot
2024-07-14 16:11 ` Thomas Petazzoni via buildroot [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=20240714181101.20b59529@windsurf \
--to=buildroot@buildroot.org \
--cc=peterlin@andestech.com \
--cc=thomas.petazzoni@bootlin.com \
/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