Hector Martin / Héctor Martín Cantero / @marcan42 / マルカン / @marcan42x / @marcan@treehouse.systems / Asahi Lina / Asahi Linux - Developer of Asahi Linux with a VTuber persona. Made Byuu's death unbelievable. Constantly accuses others of harassment and abuse. Hates Hacker News and Kiwi Farms.

[Nobody Important]

Ragequit!

Spoiler: text

I no longer have any faith left in the kernel development process or
community management approach.

Apple/ARM platform development will continue downstream. If I feel like
sending some patches upstream in the future myself for whatever subtree
I may, or I may not. Anyone who feels like fighting the upstreaming
fight themselves is welcome to do so.

Signed-off-by: Hector Martin <marcan@marcan.st>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.*
F: sound/soc/codecs/ssm3515.c

ARM/APPLE MACHINE SUPPORT
-M: Hector Martin <marcan@marcan.st>
M: Sven Peter <sven@svenpeter.dev>
R: Alyssa Rosenzweig <alyssa@rosenzweig.io>
L: asahi@lists.linux.dev
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250207-rm-maint-af7cccc22871
Best regards,
--
Hector Martin <marcan@marcan.st>

https://lkml.org/lkml/2025/2/7/9

 

[Markass the Worst]

Ragequit!

View attachment 6950230

Spoiler: text

I no longer have any faith left in the kernel development process or
community management approach.

Apple/ARM platform development will continue downstream. If I feel like
sending some patches upstream in the future myself for whatever subtree
I may, or I may not. Anyone who feels like fighting the upstreaming
fight themselves is welcome to do so.

Signed-off-by: Hector Martin <marcan@marcan.st>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.*
F: sound/soc/codecs/ssm3515.c

ARM/APPLE MACHINE SUPPORT
-M: Hector Martin <marcan@marcan.st>
M: Sven Peter <sven@svenpeter.dev>
R: Alyssa Rosenzweig <alyssa@rosenzweig.io>
L: asahi@lists.linux.dev
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250207-rm-maint-af7cccc22871
Best regards,
--
Hector Martin <marcan@marcan.st>

https://lkml.org/lkml/2025/2/7/9

I feel like he will still contribute. He will just call himself "Asahi Lina".

 

[The Taxman]

Ragequit!

View attachment 6950230

Spoiler: text

I no longer have any faith left in the kernel development process or
community management approach.

Apple/ARM platform development will continue downstream. If I feel like
sending some patches upstream in the future myself for whatever subtree
I may, or I may not. Anyone who feels like fighting the upstreaming
fight themselves is welcome to do so.

Signed-off-by: Hector Martin <marcan@marcan.st>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.*
F: sound/soc/codecs/ssm3515.c

ARM/APPLE MACHINE SUPPORT
-M: Hector Martin <marcan@marcan.st>
M: Sven Peter <sven@svenpeter.dev>
R: Alyssa Rosenzweig <alyssa@rosenzweig.io>
L: asahi@lists.linux.dev
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250207-rm-maint-af7cccc22871
Best regards,
--
Hector Martin <marcan@marcan.st>

https://lkml.org/lkml/2025/2/7/9

Don’t let the door hit ya where the good lord split ya, Hector you fag!

 

[Not Real]

I feel like he will still contribute. He will just call himself "Asahi Lina".

Either that or Asahi will coincidentally stop contributing as well not too long after this crash out

 

[ellroy]

Ragequit!

View attachment 6950230

Spoiler: text

I no longer have any faith left in the kernel development process or
community management approach.

Apple/ARM platform development will continue downstream. If I feel like
sending some patches upstream in the future myself for whatever subtree
I may, or I may not. Anyone who feels like fighting the upstreaming
fight themselves is welcome to do so.

Signed-off-by: Hector Martin <marcan@marcan.st>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.*
F: sound/soc/codecs/ssm3515.c

ARM/APPLE MACHINE SUPPORT
-M: Hector Martin <marcan@marcan.st>
M: Sven Peter <sven@svenpeter.dev>
R: Alyssa Rosenzweig <alyssa@rosenzweig.io>
L: asahi@lists.linux.dev
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250207-rm-maint-af7cccc22871
Best regards,
--
Hector Martin <marcan@marcan.st>

https://lkml.org/lkml/2025/2/7/9

 

[The Real Slim Shady]

Aaaaand Notorious LBT steps in:

View attachment 6950080

Spoiler: text

On Thu, 6 Feb 2025 at 01:19, Hector Martin <marcan@marcan.st> wrote:
>
> If shaming on social media does not work, then tell me what does,
> because I'm out of ideas.

How about you accept the fact that maybe the problem is you.

You think you know better. But the current process works.

It has problems, but problems are a fact of life. There is no perfect.

However, I will say that the social media brigading just makes me not
want to have anything at all to do with your approach.

Because if we have issues in the kernel development model, then social
media sure as hell isn't the solution. The same way it sure as hell
wasn't the solution to politics.

Technical patches and discussions matter. Social media brigading - no
than\k you.

Linus

https://lkml.org/lkml/2025/2/6/1292

I can feel Torvald's rage and disgust in that email, he didn't even read it after typing because there's a typo in the last sentence.

This is very cathartic. I hope "Asahi Lina" stops contributing too.

 

[neger psykolog]

I can feel Torvald's rage and disgust in that email, he didn't even read it after typing because there's a typo in the last sentence.

This is very cathartic. I hope "Asahi Lina" stops contributing too.

I've heard that Torvald's rages used to be infamous and he would swear and all sorts of shit - sad he seems to have chilled out a bit but still funny/great that he was so on-point with what he said.

 

[ellroy]

I feel like he will still contribute. He will just call himself "Asahi Lina".

Either that or Asahi will coincidentally stop contributing as well not too long after this crash out

I posted about this back in August. Hector was having his Asahi Lina alter ego use his stream keys to contribute, so I believe the contributions where from his account but under the guise that another person was doing it (exactly zero maintainers fell for it). I think he has removed his ability to contribute up stream so his Asahi account will have to get their own keys. I'm sure when that day comes, there will be a very interesting email chain.

 

[just Reading a post]

I DID NOT QUIT THE KERNEL, THE KERNEL QUIT ME.

LMFAO
This is what you get when you try to play autistic game of thrones Hector.
You end up looking like the spiteful fag you are, when someone with actual clout shuts you down.
Now fuck off and make your enemy's list.

 

[Rullepoelse]

It's such a shame Linus has mellowed out. Would've loved to see him post that the way he would have 10 years ago.

 

[neger psykolog]

It's such a shame Linus has mellowed out. Would've loved to see him post that the way he would have 10 years ago.

I think its good to provide a link to some of his top responses for some khantext here: https://adtmag.com/blogs/dev-watch/2014/04/linus-torvalds-rants.aspx
An example of a few:

"Mauro, SHUT THE [EXPLETIVE] UP!

"It's a bug alright -- in the kernel. How long have you been a maintainer? And you *still* haven't learnt the first rule of kernel maintenance?
"Shut up, Mauro. And I don't _ever_ want to hear that kind of obvious garbage and idiocy from a kernel maintainer again. Seriously.
Fix your [expletive] 'compliance tool,' because it is obviously broken. And fix your approach to kernel programming."

"What the [EXPLETIVE], guys?

"This piece-of-[expletive] commit is marked for stable, but you clearly never even test-compiled it, did you?
"And why the hell was this marked for stable even *IF* it hadn't been complete and utter tripe? It even has a comment in the commit message about how this probably doesn't matter. So it's doubly crap: it's *wrong*, and it didn't actually fix anything to begin with.
"There aren't enough swear-words in the English language, so now I'll have to call you perkeleen vittupää just to express my disgust and frustration with this crap."

For anyone not familiar Linus Torvalds like "created Linux" or some shit and is legendary for swearing like fuck at retards in emails - you can't really argue with him since he literally created linux (email is here: https://fossbytes.com/linus-torvaldss-famous-email-first-linux-announcement/).

He took a break for a while and toned down his emails unfortunately: https://www.newyorker.com/science/e...sive-e-mails-the-creator-of-linux-steps-aside


...
“Please just kill yourself now. The world will be a better place"... I wonder what his KF username is?

 

[Edict of Expulsion]

Acting like a hysterical faggot.
Calling in Linus for a comment, and he got one.
Continues to act like a hysterical faggot.

Linus is a faggot but hector is a tranny faggot, below even niggers.

I really wonder how many of the idiots donating to Hector’s patreon will drop him over this.

He had ONE job. Just get upstream Linux support into M1. Get hardware working and shut up and submit patches.

Well the tranny compulsion of burning bridges with even loyal toadies marches on.

Chance of hector pulling a byuu and 41%-ing rose three sizes that day.

 

[reptile baht spaniard rid]

For all his bitching and moaning, all he's listed is as A maintainer of a single soundcard driver for ARM/APPLE support? Huh.

It's such a shame Linus has mellowed out. Would've loved to see him post that the way he would have 10 years ago.

He likely would have posted something similar, Martin is simply too small of an idiot for Linus to get very angry over. The famous Linus rants are universally against people Linus respects.

Anyway, are we going to get cooties from sharing a top level domain with this faggot?

(As an aside, anyone who has an in with Tim Apple has the chance to convince him to do something really fucking funny, as Apple could release all the support necessary for Linux to boot natively today - you know they have it developed internally "just in case" and btfo Martin forever.)

 

[Prokhor Zakharov]

Hector is a ridiculous bitch, a whiner, and a social media brigading asshole, but there is one thing I can agree with him on. There needs to be a movement to memory safe languages. That is well past due. Many 0-day bugs are a result of using non-memory safe languages and people making simple mistakes in such code. Using an inherently memory safe language would mitigate this problem. I understand why people continue to use non-memory safe languages, not only do more people know them at an expert level, but they have a number of advantages as a result of their long history of use. But, at some point it has to be decided to cut ties with practices that are inherently detrimental in a number of serious ways.

 

[bort420]

Hector is a ridiculous bitch, a whiner, and a social media brigading asshole, but there is one thing I can agree with him on. There needs to be a movement to memory safe languages. That is well past due. Many 0-day bugs are a result of using non-memory safe languages and people making simple mistakes in such code. Using an inherently memory safe language would mitigate this problem. I understand why people continue to use non-memory safe languages, not only do more people know them at an expert level, but they have a number of advantages as a result of their long history of use. But, at some point it has to be decided to cut ties with practices that are inherently detrimental in a number of serious ways.

the only real change I think linux should make is moving off the dogshit mailing list based contribution system onto something modern. I have like half a dozen patches and a few drivers for hw that I simply cannot be bothered to upstream since it's too annoying.

it's hard to search it too so who knows how much stuff got lost in the noise

 

[neger psykolog]

the only real change I think linux should make is moving off the dogshit mailing list based contribution system onto something modern.

hell no, this is vintage autism with vintage autists.

the moment they move to something more normal it would attract more normies and less hardcore autists

esoteric wisdom like this that is used to maintain the kernel or operating system or whatever of everything from your mobile phone to your toaster that you try to fuck each night should be gate kept as hard as fucking possible - the entry requirements should explicitly always require navigating some old-ass mailing list system to read or write anything so that they magic is not lost.

 

[just Reading a post]

He had ONE job. Just get upstream Linux support into M1. Get hardware working and shut up and submit patches.

For some reason, he is not happy with being the guy who got Linux working on the M1 Macs. He seems to want to take over the entire GNU/Linux project and have his edicts carried out.
The way he has decided to do it is to use the tranny cabal cancel culture shit. Where he tries really fucking hard to collect "dirt" on prominent maintainers and cause drama. So he can ascend the ladder.
But because his hair grows inwards in to his own brain instead of out of his head. He is fucking retarded and any plans he makes he self sabotages and fucks up like the rube he is.
He is at the same level as people who brag about getting DooM to play on baby testers and fridges. Then tries to trick people in to thinking he invented the program in the first place.
Thing is Linus Torvolds has dealt with low rank cockroaches like him before in the mailing lists. The reason why he is being polite. Is because Linus knows he is chump and he is not worth his time.

 

[Edict of Expulsion]

Two things I can’t get over is how hector is so out of it to choose a tranny mastodon site, of all sites, if it’s really true that mastodon is really hard to recreate if you lose the account. Which is hilarious. And how he is already a tranny in the wielding a social media hug box to sperg out.



Talk about absolutely building your castle on sand. A tranny 41%s? Account gone. Fights with whatever landlord in its life and gets evicted? Account gone. The wrong news item happens or the tranny has a hissy fit over who knows what, account gone.
Absolutely embarrassing nigger IQ levels.



Also for the rust implementation, accepting the kernel process necessitates doing bassackwards stuff.
The never break user space has definitely and unavoidably led to ugly code and architecture and other things have also.


You maintain two approaches, a shim that treats the existing C code as a trusted oracle since its battle tested and hardens and just politically difficult to change.
The secondly an out of tree modification for rust guarantees that modifies the c code.
Then the rest doesn’t have to know if it’s talking to the shim code or the more invasive code.

Essentially, you treat the existing C implementation as a trusted “oracle” because it’s battle-tested and stable, while acknowledging that upstream modifications to it are challenging to get accepted. In practice, you can maintain two complementary strategies:
1. Out-of-Tree Patch Set:
Here, you directly enhance the C side with additional guarantees that align with Rust’s safety requirements. This version can be used in environments where you have control over the kernel tree (or for specialized use cases) and where you’re willing to bear the extra maintenance overhead of diverging from upstream. It gives you the ability to enforce the invariants you need more robustly.
2. Upstream-Compatible Shim:
For broader acceptance and upstream integration, you implement a shim layer that sits between the Rust code and the stable C API. This shim abstracts away the unsafe details of the C implementation, presenting an interface to Rust as if it were natively designed with those guarantees. Under the hood, it still calls the well-established C code. This approach minimizes changes to the core kernel and leverages the existing, stable behavior while still giving Rust a safe and ergonomic API.

By keeping both paths, you can develop and test your Rust abstractions against a version with direct guarantees (via the out-of-tree patches) and also maintain an upstream-friendly variant that doesn’t require invasive changes to the core kernel. This dual-path strategy maximizes both safety and compatibility, allowing you to ship something useful across different environments.

In summary, a two-pronged approach—one for controlled, enhanced safety (out-of-tree) and one for upstream integration (shim)—is indeed a practical solution that balances the realities of kernel development with Rust’s safety goals.

 

[Lapsus of the bepsus]

the moment they move to something more normal it would attract more normies and less hardcore autists

problem is that this also attracts hysterical trannies like marcan who try to subvert entire projects into switching to different tech stacks and adopting CoC's catering to trannies and their attention fetish because doing things the normal way is pROblEmAtiC. they are usually deeply autistic, disturbed individuals never leaving their computer shed and having to use a communication system from the 1980s does absolutely nothing to filter them out

 

[ellroy]

Hector is a ridiculous bitch, a whiner, and a social media brigading asshole, but there is one thing I can agree with him on. There needs to be a movement to memory safe languages. That is well past due. Many 0-day bugs are a result of using non-memory safe languages and people making simple mistakes in such code. Using an inherently memory safe language would mitigate this problem. I understand why people continue to use non-memory safe languages, not only do more people know them at an expert level, but they have a number of advantages as a result of their long history of use. But, at some point it has to be decided to cut ties with practices that are inherently detrimental in a number of serious ways.

If you're contributing code with 0-days in them then that is a skill issue and you have no business contributing to the kernel. There was a solution to some of this with smart pointers when C++11 standard arrived but Linus refused to touch it. After his struggle session, he decided Rust was the best path forward when in reality it isn't because Rust standard was and remains incomplete and embedded Rust isn't memory safe; remember, Linux runs on a lot of embedded devices. I think the ones pushing for Rust the loudest are the least competent systems programmers.


The Kernel isn't perfect but its been pretty rock solid with a good security practices. The biggest vulnerabilities of recent memory are the result of social engineering, not zero days.