Posts
467
Following
143
Followers
151
The cat is not mine :(

I like cycling, powerlifting, bad video games and metal.
Otherwise, I occupy my time with various bits in RISC-V land.

~useless, placeholder, website: https://www.conchuod.ie/
It's bad enough to fail a lift at the gym and be annoyed with yourself, only to turn around and realise people were watching you :/
0
0
0
@kernellogger No? There's refactoring/cleanup, moving to a different API or switching from some arch-specific implementation to one that is generic.
Those are "safe" to revert in comparison as there may not be someone that has gained a dependency on that feature that reverting it in a previous release would break.
1
0
0
@kernellogger I don't quite follow. They're opposed to reverting a new feature or some other sort of change?
I can understand not wanting to revert the addition of a feature that landed a release ago.
What you do here totally depends on the regression and it's cause & without that context it's hard to agree/disagree.
1
0
0
@asb It's a general thanks to the LLVM community :)
The versioning stuff is a farce, I don't get to go a couple of days without having to deal with it in some project.
0
0
1
@asb Thanks for doing something reasonable with the Zicsr and Zifencei extensions!
1
0
1
Scheduling a meeting for 18-19 on a Friday is a crime.
1
0
3
@kernellogger not sure what to think of new Closes: trailer business. On one hand, the automation is nice to have but it just reeks of something that's gonna be used inconsistently.
1
0
1
@nathanchance @brauner @horms @gregkh @monsieuricon I was talking about branch descriptions, and format-patch's --cover-from-description argument. I don't doubt that b4 is easier though.
0
0
1
Since there's no quote-rt here: https://fosstodon.org/@nathanchance/110113218822882839

Speaking of workflow, I need to figure out a workflow for auto-generating "do change x in 40 different places as 40 commits".
0
0
1
@nathanchance @gregkh @brauner @horms @monsieuricon "you can embed the recipients of the series/patch into the cover letter once" to be fair, you can do this using git alone.
Been putting off using b4 for sending, I kinda wanna see what someone's workflow looks like before switching.
2
0
1
@ljs it's not been that cold this winter actually - but one of the worst bits is where they've removed road markings, leaving the tiniest of ruts. Over the course of the winter freeze/thaw and the traffic converted a barely noticeable bit of damage into quite a deep crack. It's become like cycling over a tramline, need to be very careful on a bike with slim tyres!
1
0
2
Edited 1 year ago
A cross city infrastructure project means each day brings new damage to the road surface, some bits look up to 10 cm deep.
If I wanted to roll the dice on serious injury or death, I'd commute on my track bike..
1
0
1
@brauner @gregkh @monsieuricon Aye, the b4 ones are rather nice. Certainly nicer than what you get out of git send-email, or god forbid, gmail.
0
0
0
Note to self: failure to acquire a toolchain should fail the pipeline, not try to run the builds and publish failed results against those patches..
0
0
2
Upgrade CI toolchain, typo - instead of _ in filename, wake up to a wall of red, whoops.
1
0
0
@marcan Oh wow, that's another level of pain entirely. I've got a nice (attempted) backtrace on boot to help me out!
0
0
0
@marcan I'm super curious what the (eventual) reaction from Jassi is going to be. My mailbox driver was the first that I wrote and I am far from proud of it (first driver and the client was in a review blackspot), but I'm very much in the 1:1 situation that you are.
I'd like to entirely re-write the thing, but if I do that I'd be inclined to make the thing a single driver, especially since getting mailbox code in is often on the slower side :(
0
0
2
@codonell I literally deleted all my email this morning and just replied to IRC/mastodon posts...
0
2
4
@palmer @krzk Ohh, and W=1 for dtbs_check isn't too bad, there's one known issue w/ the renesas bits that's waiting on dma bits.
0
0
0
Show older