@rpardini https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ but watch out, it's rebased all the time.

But, 6.1.140 is already released, why not just use the normal stable git tree for that?

COBOL c:

Another podcast interview with me from a few weeks ago:
https://www.youtube.com/watch?v=DZzFG_zhFnY
that focuses a lot on the corporate interaction and involvement in open source projects.

Really excited for Zim's talk at Embedded Recipes showing off all the cool things Perfetto can do! It's a really useful tool.

I helped with one of the examples, and had seen the slides prior, but even so, I *still* learned some new tricks from watching.

https://www.youtube.com/live/802-CNevuY8?feature=shared&t=7608

#LLMs are not a knowledge base!

Stop spreading misinformation!

They are statistical models that _simulate_ knowledge!

We, as a #society, really have to pay attention to the words and #language we're using.

But I guess, when talking about LLMs, details are not really important, are they!? Oh, such beautiful irony!

#LLM #SALAMI

"If all these big companies are shouting from the rooftops that AI is up to production code the money relies on, then zero open source contributions of substance is a glaring absence."

(Original title: If AI is so good at coding … where are the open source contributions?)

https://pivot-to-ai.com/2025/05/13/if-ai-is-so-good-at-coding-where-are-the-open-source-contributions/

@embeddedrecipes has just kicked off!

New organizers are running the show this year — big thanks to BayLibre for picking up the torch and keeping the spirit of Recipes alive: small-scale, sharing, and real exchange.

You can follow the conference live!

https://www.youtube.com/live/U5L8XHkP-lI?feature=shared

The 2025 edition of @embeddedrecipes starts with @gregkh
https://www.youtube.com/live/U5L8XHkP-lI?si=h5-X2I97Rnb1hey8
#er2025 #embeddedrecipes

Long but cheering+ practical from @bert_hubert

https://berthub.eu/articles/posts/a-coherent-non-us-cloud-strategy/

"Europe has ample compute capacity and skills.... the carrot won’t be enough to make Europe sovereign again. We must have our own technology under our own control, but we must also make sure that it gets used"

@ljs I'm confused, AUTOSEL is there to pick up stuff that people don't tag that look like other bug fixes, it was created because many subsystems/maintainers do NOT tag anything, so this is needed to get those fixes.

For subsystems/authors that do properly tag them, and don't want to get picked up by AUTOSEL, let us know and they can be added to the list not to.

I thought that is what you were referring to here, if not, then I think it's time to just discuss it over beers in person :)

@ljs If you don't want stuff picked up by AUTOSEL, let us know and you can be added to the regex of files / directories to ignore. Many subsystems do as they do properly tag stuff. But for all the others, that's why AUTOSEL is there.

Sasha's "AUTOSEL" logic has been revamped and published so that now you too, can dig in the Linux kernel commit logs to find patches that developers and maintainers forgot to tag to be backported to stable kernels:

The announcement:
https://lore.kernel.org/all/aBj_SEgFTXfrPVuj@lappy/

And the code itself:
https://git.sr.ht/~sashal/autosel

@mansr @broonie @geert It's a bot, and it is saying "next time, please properly mark this for stable backport as that is what you are saying you want to have happen, but yet that's not what is going to happen with the tags you provided".

If you can think of better wording for this, please let me know. Don't take bots personally please, they are trying to help.

@geert @mansr @broonie No, it's not guaranteed to be backported at all, cc: stable is still required if you want it to show up AND want to be notified if it does not apply. We get to "Fixes:" only patches on a "when we have the spare cycles let's go look for things that people did not properly mark and attempt to do a backport if it works easily"

Good programming is 99% sweat and 1% coffee.

— anonymous

#programming

Psst, hey: HACKERS ARE NOT TECH BROS. The vast majority of hackers never become tech bros. The ethics of hacking runs completely counter to that of tech bros.

Hackers make hardware do things they weren’t intended to do. They circumvent barriers. They string together contraptions that repurpose old stuff to do new things. Hackers aren’t that interested in money; they’re more interested in showing off their skills. They love to learn and make demos and create and share free tech that other hackers then build upon. All they want is acknoweledgement and the respect of their peers.

Tech bros are parasites. They’re greedy bastards who love to erect barriers between people and tech. They extract, addict, monetize. They turn everything fun and useful into a transaction, a dopamine trap, a subscription, a surveillance tool, an advertising outlet, and a vector to extract money from labor and suppliers.

Please don’t get them mixed up.

#hackers #hacking #techbros

@siteshwar Then someone at RHEL knows enough not to bother open source projects with obviously broken and illogical reports like that. Maybe they should have worked with the Fedora people first before sending all of this out.

@kasperd @fenruspdx Then send a real patch, as a "fix" and have the developers involved review it like any other normal type of fix that is submitted. Do NOT make a maintainer have to wade through a random report from a random tool that is filled with obviously broken and wrong reports just with the hope that maybe one of them might actually be a real issue.

In other words, do the work of weeding out the wrong reports on your end, don't ask others to do work for you just because you found the output of a free tool.

Maintainers and projects are drowning in "reports" like this, and we all have just started to totally ignore them and classify them as junk. If you don't want us to do that, then actually submit fixes instead.

This ordinary Tuesday? Two. Two AI slop security reports arrived to #curl. So far.

@kasperd None.

Have someone actually verify that they are real issues before "reporting" them to a project.

But better yet, submit a patch fixing them if you have found and determined that they are a real issue, that's the only way for anyone to take reports like this seriously.

Otherwise, it's just noise.