ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
	corbet@lwn.net, ksummit@lists.linux.dev,
	 linux-kernel@vger.kernel.org,
	tech-board-discuss@lists.linux.dev,
	 Linus Torvalds <torvalds@linux-foundation.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Miguel Ojeda <ojeda@kernel.org>,  Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] Documentation: Project continuity
Date: Sat, 24 Jan 2026 12:17:49 +0100	[thread overview]
Message-ID: <CANiq72muqOW=uMwtAG3753v6fkakXSO31zy2NBGd6GH4neFewQ@mail.gmail.com> (raw)
In-Reply-To: <20260124082939.40715e13@foz.lan>

On Sat, Jan 24, 2026 at 8:29 AM Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Also, if there were no kernel summit in the last year (*), TAB may not

Quick note on the TAB elections: while they typically happen
during/around the KS/LPC, it is not a hard requirement, and we briefly
discussed potentially changing that (unrelated to this document).

So if a KS didn't happen (or was moved to a significantly different
time of the year) for some reason, then we would likely need to do
elections anyway.

Cheers,
Miguel

  parent reply	other threads:[~2026-01-24 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24  1:22 Dan Williams
2026-01-24  7:29 ` Mauro Carvalho Chehab
2026-01-24  9:31   ` Greg Kroah-Hartman
2026-01-24 11:17   ` Miguel Ojeda [this message]
2026-01-24 20:45   ` Jiri Kosina
2026-01-24 22:43 ` Linus Torvalds
2026-01-24 22:47   ` Jiri Kosina
2026-01-24 23:58 ` Steven Rostedt
2026-01-26  2:08 ` Shuah
2026-01-26  3:19 ` Julia Lawall
2026-01-27 14:34 ` Linus Walleij

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='CANiq72muqOW=uMwtAG3753v6fkakXSO31zy2NBGd6GH4neFewQ@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kees@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=tech-board-discuss@lists.linux.dev \
    --cc=torvalds@linux-foundation.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