Resigning as Asahi Linux project lead
-
apart from the Mojo thing you it wasn't clear that this was only your experience, and none of which are accurate or useful observations
-
I’m not at a computer with the source on it, so if you get to it before me, how many rust drivers are there? How many that would use the rust dma wrapper?
I ask because last year there were relatively few.
People writing in c don’t have to use a wrapper because there’s no need to wrap c code for use by other c code.
More broadly there are times when duplicated c code has been condensed into a library or something and added to the kernel.
-
I’m not at a computer with the source on it, so if you get to it before me, how many rust drivers are there? How many that would use the rust dma wrapper?
... of course there aren't many Rust drivers so far, since the project is still young, and it's evidently still facing hurdles and not really accepted by everyone. But if there's already a couple of Rust drivers and Rust has explicitly been accepted into the Kernel, we're already past your “this would make it easier for hypothetical rust drivers that might hypothetically exist in the future”, so why argue such irrelevant points?
More broadly there are times when duplicated c code has been condensed into a library or something and added to the kernel.
And that's what has been blocked here...
-
Going to need you to cite your sources on that one. https://www.adelaidenow.com.au/sport/football/the-major-flaw-with-racial-charge-against-sam-kerr-that-shouldve-seen-the-case-abandoned/news-story/62e5fad93d835c9f432923375e5e833d
-
In the same way a swastika is no longer linked to an ancient peace symbol.
-
Can a maintainer really NACK any patch they dislike? I mean I get that Hellwig said he won't merge it. Fine. What if for example Kroah-Hartmann says "whatever, I like it" and merges it nonetheless in his tree?
-
Linus is pro-Rust. It is not clear from what you wrote that you realize that. He has merged plenty of Rust code. I personally expect him to merge the change that caused all this current drama (though I could clearly be wrong about that).
Right or wrong, this is how Linux kernel dev has always worked. How long did it take for real time to get in? How smoothly is the bcachefs merge going? Have you read any of the GPU driver chatter?
Honestly though, it is not just the kernel. How much different is the Wayland scene?
I am hardly defending Linux here by the way. I think the maintainers are blocking progress. I am merely pointing out that it is hardly new or unique.
Anyway, RedoxOS is quite progressive. They would probably love help from anybody that finds Linux kernel dev too stodgy.
-
I doubt Greg is pulling in Rust until it has been through the mainline. That said, Linus can merge anything he wants.
-
If we are going to be honest, let’s not be misleading.
Nobody is looking to replace C in the kernel. This is not a “rewrite it in Rust” initiative.
What the R4L folks want is to be able to write “new” code in Rust and for that code to calling into the C parts of the kernel in an idiomatic way (idiomatic for Rust). So they need to create Rust interfaces (which they, the R4L side, or doing). This whole controversy is over such an example.
At this point, we are talking about platform specific drivers.
Now, new kernel code is written all the time. Sometimes newer designs replace older code that did something similar. So yes, in the future, that new code may be written in Rust and replace older code that was written in C.
Core kernel code is not getting written in Rust for a while though I do not think. For one thing, Rust does not have broad enough architecture support (platforms). Perhaps if a Rust compiler as part of GCC reaches maturity, we could start to see Rust in the core.
That is not what is being talked about right now though. So, it is not a reasonable objection to current activity.
-
GNOME is not user-centric. GNOME is GNOME-centric.
-
It was an example. I don't have a fucking clue how all the maintainers are named.
The main question was: why can a maintainer NACK something not in their responsibility? Isn't it simply necessary to find one maintainer who is fine with it and pulls it in?
Or even asked differently: shouldn't you need to find someone who ACKs it rather than caring about who NACKs it?
-
If that does happen, I just hope there will be enough developers by then that can/will want to use it (as in, write rust code). Especially developers that can put up with the kernel process and its people.
-
If R4L authors want to use Rust so badly, then still:
Maintain your own tree! Let's see how simple and clean these interfaces are over the longer haul.
They will get mainlined if they are technically superior.
-
Take this case, it all started over a bit of code. The subsystem maintainer refuses to take it. But it does not require any changes to existing code. It just has to be merged.
Linus can take it directly. If he does that, the Rust folks can start to use it. The sub-system maintainer will lose in the end.
At some point, the battle will be lost by those trying to block Rust.
It all depends on Linus. We will see.
Linus hasn't been merging the necessary code, by virtue of supporting a maintainer who was very obviously trying to sabotage R4L; if Linus was going to stand up for R4L, this would have been the time.
-
Linus can merge whatever patches he wants to, and the stonewalling subsystem maintainers would have to deal with it--like he did with the eBPF scheduler. R4L maintainers already wrote the patches, they literally just needed to be merged.
-
Slightly OT but I always thought Asahi Lina was a woman. TIL.
-
You're probably right from a legal perspective, but the difference between "donation" and "salary" is pretty murky in this context.
-
Yes, but asking him in this case was basically a courtesy, the code isn't going into anything he manages. He can reject it, but that's an opinion, not a decision. It can still be merged if the regular maintainer (or someone senior like Linus himself) approves.
-
It was merged into mainline, in 6.1, over a year ago.
-
People are not under sanctions, and no linux developer worked for the Russian government, and since when has a war affected who works on what open source project. There are wars all over the place all the damn time ..
I am not talking about the sanctions, I am talking about the additional remarks on how nationalist and racist both the leaders of the project appeared to be from their statements.
