From: Francesco Valla <valla.francesco@gmail.com>
To: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>,
"Bird, Tim" <Tim.Bird@sony.com>
Subject: Re: [boot-time] RFC: proposal for boot-time tools github repository
Date: Sun, 03 Nov 2024 17:15:50 +0100 [thread overview]
Message-ID: <2523504.XAFRqVoOGU@fedora.fritz.box> (raw)
In-Reply-To: <MW5PR13MB5632D76A85C2DCE48B5AA2B4FD542@MW5PR13MB5632.namprd13.prod.outlook.com>
On Wednesday, 30 October 2024 at 09:22:09 Bird, Tim <Tim.Bird@sony.com> wrote:
> I have a few tools that I plan to publish over the next little while.
>
> Some of these might make their way into the kernel 'scripts' directory, but some
> others of these might not be appropriate to add there.
>
> So I'm thinking of putting together a repository of boot-time related tools
> for people to play with. Here's a sample of one tool that I find handy:
> ----
> #!/bin/sh
> # sort-initcalls.sh - sort the initcalls by duration
>
> if [ -z "$1" -o "$1" = "-h" ] ; then
> echo "Usage: sort-initcalls.sh <dmesg file>"
> exit 1
> fi
>
> grep "initcall.*after" $1 | sed "s/\(.*\)after\(.*\)/\2 \1/g" | sed "s/\r//" | sort -n
> ----
> See https://elinux.org/Initcall_Debug for details.
>
> For tools on their way upstream, this would serve as a development repository
> where different ideas and techniques can get hashed out.
>
> So, does anyone have alternative ideas for hosting such tools, or comments on
> this approach?
Sounds fine, at least from the perspective of a developer not so much expert
on the whole mainline development flow (like me).
Were you thinking of using the Github PR method to accept contributions?
Greetings,
Francesco
next prev parent reply other threads:[~2024-11-03 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 8:22 [boot-time] RFC: proposal for boot-time tools github repository Bird, Tim
2024-11-03 16:15 ` Francesco Valla [this message]
2024-11-05 2:04 ` Bird, Tim
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=2523504.XAFRqVoOGU@fedora.fritz.box \
--to=valla.francesco@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=linux-embedded@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).