From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomasz Figa <tfiga@chromium.org>
Cc: Daniel Almeida <daniel.almeida@collabora.com>,
Hidenori Kobayashi <hidenorik@chromium.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sean Young <sean@mess.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Sebastian Fricke <sebastian.fricke@collabora.com>,
Ricardo Ribalda <ribalda@chromium.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: [ANN] Request for Topics and registration for a Media Summit September 16th
Date: Wed, 12 Jun 2024 10:46:32 +0300 [thread overview]
Message-ID: <20240612074632.GB28989@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAAFQd5Ae7ctMiPWw1=ugeVCFhTJYbNQ_G2xnoOoc-EYRqp4B2A@mail.gmail.com>
Hi Tomasz,
On Wed, Jun 12, 2024 at 01:12:29PM +0900, Tomasz Figa wrote:
> On Wed, May 15, 2024 at 1:19 AM Daniel Almeida wrote:
> >
> > Hi Hans, all,
> >
> > I’d like to attend in person and discuss the use of Rust in the subsystem, especially in light of [0] and [1].
> >
> > Please note that these are new submissions that are unrelated with what was discussed last year.
> >
> > 30 minutes will do.
> >
> > [0] https://lwn.net/ml/linux-media/20240227215146.46487-1-daniel.almeida@collabora.com/
> > [1] https://lwn.net/Articles/970565
>
> Somewhat related to the topic: I see potential for a quite big
> redesign of the videobuf2 framework going forward and recently with
> more Rust adoption I'm starting to think it could benefit from being
> implemented in Rust, since we would have to rewrite it quite a bit
> anyway. Especially since it's a part of the subsystem that has to deal
> with memory management, object lifetime and asynchronousness quite a
> lot and we had a history of issues there. So it could be interesting
> to hear everyone's thoughts.
More than the language choice, what picked my interest here is why you
htink vb2 should be rewritten. Do you have a high-level overview
document that explains the rationale and what you think the new vb2
should look like ?
> That said, I wouldn't be able to travel this time unfortunately, so it
> would be nice if we could arrange this topic in a time slot friendly
> for remote attendance from Japan. Also +Hidenori Kobayashi from my
> team who would also be interested in joining remotely.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-06-12 7:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 11:33 [ANN] Request for Topics and registration for a Media Summit September 16th Hans Verkuil
2024-05-06 11:40 ` Ricardo Ribalda
2024-05-06 12:31 ` Laurent Pinchart
2024-05-06 13:32 ` Sean Young
2024-05-07 6:40 ` Tommaso Merciai
2024-05-08 7:16 ` Hans Verkuil
2024-05-08 12:19 ` Tommaso Merciai
2024-05-14 16:16 ` Daniel Almeida
2024-06-12 4:12 ` Tomasz Figa
2024-06-12 6:46 ` Hans Verkuil
2024-06-12 7:10 ` Steve Cho
2024-06-12 7:54 ` Mauro Carvalho Chehab
2024-06-12 8:22 ` Tomasz Figa
2024-06-12 8:34 ` Laurent Pinchart
2024-06-12 9:01 ` Tomasz Figa
2024-06-12 9:20 ` Laurent Pinchart
2024-06-12 9:33 ` Tomasz Figa
2024-06-12 9:40 ` Laurent Pinchart
2024-06-12 20:09 ` Nicolas Dufresne
2024-06-12 20:19 ` Laurent Pinchart
2024-06-13 7:17 ` Chen-Yu Tsai
2024-06-12 20:44 ` Mauro Carvalho Chehab
2024-06-12 20:52 ` Laurent Pinchart
2024-06-13 7:08 ` Hans Verkuil
2024-06-13 9:12 ` Laurent Pinchart
2024-06-13 9:38 ` Hans Verkuil
2024-06-13 9:59 ` Laurent Pinchart
2024-06-12 20:35 ` Mauro Carvalho Chehab
2024-06-13 7:38 ` Hans Verkuil
2024-06-13 8:14 ` Tomasz Figa
2024-06-13 8:35 ` Hans Verkuil
2024-06-13 10:08 ` Laurent Pinchart
2024-06-12 8:06 ` Tomasz Figa
2024-06-12 7:46 ` Laurent Pinchart [this message]
2024-05-15 9:32 ` Hans Verkuil
2024-06-04 21:48 ` Steve Cho
2024-06-17 12:43 ` Hans Verkuil
2024-06-19 9:28 ` Tomasz Figa
2024-06-28 11:59 ` Sakari Ailus
2024-07-16 13:11 ` Sakari Ailus
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=20240612074632.GB28989@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=daniel.almeida@collabora.com \
--cc=hidenorik@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sean@mess.org \
--cc=sebastian.fricke@collabora.com \
--cc=tfiga@chromium.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).