From: "Bird, Tim" <Tim.Bird@sony.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Linux Embedded <linux-embedded@vger.kernel.org>
Subject: RE: [boot-time] Unified Boot Log - special topic call for Boot-Time SIG (meeting announcement)
Date: Wed, 21 May 2025 20:47:06 +0000 [thread overview]
Message-ID: <MW5PR13MB56320C5883FEC27C49C7F296FD9EA@MW5PR13MB5632.namprd13.prod.outlook.com> (raw)
In-Reply-To: <CAGETcx9S2nyz00G3fq1taz9QEshpTPmaUX_+=FyHzzj--ELEXg@mail.gmail.com>
> -----Original Message-----
> From: Saravana Kannan <saravanak@google.com>
> Hi Tim,
>
> Could you send out these reminders 2 days earlier? I always miss them and see them later in the day on Tuesdays and regret not being able to
> attend it. It has happened at least 3 times so far.
Yes. I'll try to get these reminders out earlier. I apologize these have been so late.
My goal is to send the reminder the week before (like Wednesday or Thursday), but
I was traveling last week and got behind.
>
> Another option is to have some calendar that people could subscribe to.
I should look into that. My process leaves something to be desired.
I appreciate you reminding me to improve my process here!
Regards,
-- Tim
> On Mon, May 19, 2025 at 9:23 AM Bird, Tim <Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> > wrote:
>
>
> Hey Linux Boot-Time SIG interested parties (and other interested Linux kernel developers),
>
> Here is the information for the next Linux Boot-Time SIG conference call.
>
> This call is a "special topic" call, on the subject of Unified Boot Log.
> See https://elinux.org/Unified_Boot_Log
>
> The meeting will be held via the Jitsi online meeting platform.
> To Join the meeting via web, click on:
> https://meet.jit.si/LinuxBootTimeSIG
>
> ----
> The meeting is Tuesday, May 20, at 9:00 am Mountain Daylight Time.
> See this link for other time zones:
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2025&month=05&day=20&hour=15&min=0&sec=0&p1=220&
> p2=137&p3=195&p4=771
> (That makes it 8:00 am Pacific, 15:00 UTC, 17:00 CEST, and 20:30 IST)
>
> Please note that this is NOT our regularly scheduled monthly SIG call, which is next week.
>
> I'm planning on 30 minutes for this meeting, but I can go longer if the discussion warrants.
>
> The agenda for the meeting (and where we'll keep the minutes) is here:
> https://docs.google.com/document/d/1XAufoTT6VVJOTMzKMoz8SyOss-JA9H4J1_yVXQq5mN0/edit?usp=sharing
>
> The agenda for this meeting is:
> - Discuss issues with the Unified Boot Log
> - review elinux page: https://elinux.org/Unified_Boot_Log
> - discuss existing/related efforts:
> - U-Boot's boot-stage: https://github.com/u-boot/u-boot/blob/master/include/bootstage.h
> - RedHat's boot-time-analysis tools: (cntvct and boot-time)
> - https://gitlab.com/CentOS/automotive/src/boot-time-analysis-tools
>
> I look forward to talking with you in the meeting.
> -- Tim
>
>
prev parent reply other threads:[~2025-05-21 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 15:58 [boot-time] Unified Boot Log - special topic call for Boot-Time SIG (meeting announcement) Bird, Tim
[not found] ` <CAGETcx9S2nyz00G3fq1taz9QEshpTPmaUX_+=FyHzzj--ELEXg@mail.gmail.com>
2025-05-21 20:47 ` 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=MW5PR13MB56320C5883FEC27C49C7F296FD9EA@MW5PR13MB5632.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=linux-embedded@vger.kernel.org \
--cc=saravanak@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).