linux-kernel - Re: On community influencing (was Re: [PATCH v8 2/2] rust: add dma coherent allocator abstraction.)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEg-Je9BiTsTmaadVz7S0=Mj3PgKZSu4EnFixf+65bcbuu7+WA@mail.gmail.com>
Date: Fri, 14 Feb 2025 02:10:57 -0500
From: Neal Gompa <neal@...pa.dev>
To: Mark Brown <broonie@...nel.org>
Cc: Hector Martin <marcan@...can.st>, Konstantin Ryabitsev <konstantin@...uxfoundation.org>, 
	Danilo Krummrich <dakr@...nel.org>, Dave Airlie <airlied@...il.com>, Jason Gunthorpe <jgg@...dia.com>, 
	Greg KH <gregkh@...uxfoundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, 
	phasta@...nel.org, Christoph Hellwig <hch@....de>, 
	Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, 
	Abdiel Janulgue <abdiel.janulgue@...il.com>, daniel.almeida@...labora.com, 
	aliceryhl@...gle.com, robin.murphy@....com, rust-for-linux@...r.kernel.org, 
	Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Trevor Gross <tmgross@...ch.edu>, Valentin Obst <kernel@...entinobst.de>, 
	open list <linux-kernel@...r.kernel.org>, Marek Szyprowski <m.szyprowski@...sung.com>, 
	David Airlie <airlied@...hat.com>, 
	"open list:DMA MAPPING HELPERS" <iommu@...ts.linux.dev>, DRI Development <dri-devel@...ts.freedesktop.org>
Subject: Re: On community influencing (was Re: [PATCH v8 2/2] rust: add dma
 coherent allocator abstraction.)

On Mon, Feb 10, 2025 at 12:28 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Sun, Feb 09, 2025 at 03:25:26AM -0500, Neal Gompa wrote:
> > On Friday, February 7, 2025 1:16:11 PM Eastern Standard Time Konstantin
> > Ryabitsev wrote:
>
> > > It is my goal to be able to give subsystems a way to use forges without it
> > > impacting how they interact with upstream or handle tree-wide changes. That
> > > is, once I'm done moving things from one Benevolent Company to another.
>
> > Honestly, this is probably not possible. If a subsystem moves to a forge
> > workflow, it pretty much means tree-wide changes need to work partially that
> > way too.
>
> We do actually have some people using forges already, for example the
> SOF people do a bunch of their review on github and then turn that into
> patch serieses which they send via the normal email route when they're
> happy with them.  I think tree wide stuff flows in via back merges or
> rebases, one of the benefits of delegation is that it's not my problem.
> This all works perfectly well from my side, as far as I know it's fine
> for the SOF people too.  It certainly doesn't seem insurmountable.

It might be working as long as a subsystem continues to allow
receiving patches via email. As soon as a subsystem decides to stop
doing that (which is absolutely their right given the model of
subsystem maintenance that the Linux project has), I think this will
break down very quickly.

I wonder which team will be the first one to do it. It's not a
question of if, but when.


-- 
真実はいつも一つ！/ Always, there's only one truth!