linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bird, Tim" <Tim.Bird@sony.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [boot-time] RFC grab-boot-data.sh - tool to grab boot time data
Date: Wed, 27 Nov 2024 19:20:01 +0000	[thread overview]
Message-ID: <MW5PR13MB563217F05913D7146437B395FD282@MW5PR13MB5632.namprd13.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdWUMap1maZCmOqEqaxNWHKRiwg1QaN0W9j+8iPkPyHEMg@mail.gmail.com>



> -----Original Message-----
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> Hi Tim,
> 
> On Thu, Nov 7, 2024 at 2:26 AM Bird, Tim <Tim.Bird@sony.com> wrote:
> > I'm writing to introduce a tool that I'd like people to run, to gather boot-time data on
> > their systems.  I'd like to collect boot-time data from a lot of different systems.
> 
> [...]
> 
> Thank you!
> 
> > ---- script grab-boot-data.sh follows ----
> > #!/bin/sh
> > # grab-boot-data.sh
> 
> It's always a good idea to run shellcheck on any script you write.

Thanks.  I went through the issues reported by shellcheck and adjusted
a few things.

The tool currently lives at: https://birdcloud.org/boot-time/Boot-time_Tools
but I anticipate creating, soon, a github repo for this and other tools, and possibly
non-upstreamable (or on-their-way-to-upstream) patches.
 -- Tim

      reply	other threads:[~2024-11-27 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  1:26 [boot-time] RFC grab-boot-data.sh - tool to grab boot time data Bird, Tim
2024-11-07  7:41 ` Geert Uytterhoeven
2024-11-27 19:20   ` Bird, Tim [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=MW5PR13MB563217F05913D7146437B395FD282@MW5PR13MB5632.namprd13.prod.outlook.com \
    --to=tim.bird@sony.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-embedded@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 read-only IMAP folder(s) and NNTP newsgroup(s).