From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: workflows@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hallway BoF at LPC about generative AI for kernel development
Date: Sun, 4 Oct 2026 19:33:28 +0200 [thread overview]
Message-ID: <20261004173328.GB533673@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20261004172533.GA533673@killaraus.ideasonboard.com>
And of course the subject line should have read "Hallway BoF at LPC
about generative AI for kernel development". I need to learn to
proof-read the subject too.
On Sun, Oct 04, 2026 at 07:25:35PM +0200, Laurent Pinchart wrote:
> Hello,
>
> In preparation for the maintainer summit, I have issued a call for
> opinions regarding usage of generative AI for kernel development ([1]).
> Multiple people expressed an interest in discussing this topic face to
> face in Prague during LPC (you are all BCC'ed to this e-mail).
>
> As this topic is orthogonal to most of the discussions that will take
> place at LPC, I don't expect to find a time that will suit everybody. I
> will try to organize multiple "hallway BoFs" to give as many people as
> possible a chance to join. If you would like to participate in the first
> one, look for me during the Monday morning break at 11:30 in the foyer
> in front of the Club A room. We may continue the discussion into the
> next slot, possibling grabbing a BoF room if available.
>
> I will relay this annoucement on Mastodon and in the LPC Hallway Track
> matrix room. Please keep an eye on the matrix room on Monday morning, I
> will post updates there in case last minute changes are required.
>
> [1] https://floss.social/@pinchartl/117320477532952626
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-10-04 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 17:25 Hallway BoF at LPC about Laurent Pinchart
2026-10-04 17:33 ` Laurent Pinchart [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=20261004173328.GB533673@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@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
all inboxes | Powered by JetHome®