User Details
- User Since
- Aug 29 2014, 12:11 PM (637 w, 5 d)
Wed, Nov 11
Sun, Nov 8
Mon, Nov 2
I'd suggest to reduce it to this.
The ath11k explanation in the commit message is for ath11k but not generic LinuxKPI. There's a further issue if the commit message is correct to be dealt with as the native PCI stack, I believe tracks MSI state (also for resume) and may not be able to do so?
Adding @dumbbell as msix will change behaviour for amdgpu I believe; msi is indeed ath11k only currently. I'll deal with this as soon as I have stable internet again (as one notices as the submit didn't work the first time).
Sat, Oct 31
You'll have to explain WHY this is possibly fixing the problem. Usually deferred contexts are not the right solutions to fix ordering problems (if that's what it would be)?
Fri, Oct 30
Tue, Oct 20
Thanks for the feedback. I'll wait for @markj
Would it be too much if I asked to do the factoring out of sdda_set_host_ios() upfront?
Mon, Oct 19
I'll have to go and look; I wonder if there was a mis-merge somewhere. Due to other generic LinuxKPI changes which were in review for quite a long time I had to rebase the entire code back then to get it in and only the recent changes (which were backed out as they broke drm-kmod as we know) would actually make all the lock assertions work again on a GENERIC kernel.
Oct 19 2026
Sorry for saying it that way:
Oct 17 2026
Oct 14 2026
Firmware goes to ports these days. Use fwget to install it.
Oct 13 2026
This seems to be the "final" version to review given the parent review is accepted.
Oct 12 2026
Adding @dumbbell given the recent drm-kmod build issues after my changes to LinuxKPI as this will be interesting there (though a lot harder to introduce given drm-kmod also needs to compile on older branches).
Oct 11 2026
Adjust the code to LINUXKPI_FEATURES+= and add futher support.
Needless to say this makes the feature options also nicly grep-able.
Oct 10 2026
Oct 9 2026
Oct 8 2026
Oct 6 2026
What if I'll change it one step further and call it LINUXKPI_ADD and we add GENSRC to that too along with INCLUDES?
Add the one from @emaste (thanks!) while still here.
@emaste what's your VID combination?
Add another user supplied entry.
Oct 4 2026
Alos please change the first line of the commit message to
LinuxKPI: firmware: ....
I've done the due diligence and it seems for all LinuxKPI versions we care about we can apply this.
Oct 3 2026
Oct 2 2026
This is not ideal yet and I hope you can help me to get it polished and move things in the right place but it feels a lot better (at least to me) having one source of truth rather than (n+1) man pages with a copy of the (longer) text.
Oct 1 2026
Careful! We already have a native uuid_t! Someone should check if (a) we can use that and (b) possible conflict potential.
Please note there are a lot of commented out parts in there for drivers, etc. which do use LinuxKPI, which are in the tree, but not yet hooked up to the build.
I found out why this was not really working. I'll put a review up for fixing LINUXKPI_INCLUDES as soon as I put down linuxkpi.9 to document it.
Sep 30 2026
Anyone on this fairly simple review?
Superseded by D59913
I have an old (non-stack) stack open (I believe from 2018) of which you would have been a reviewer:
Sep 26 2026
Ok, very last call. It's not been December in almost a year soon and May is also gone for a while. 48 hours.
Can you please upload this with either arc or a patch from git diff -U9999 so context is available.
Sep 24 2026
Sep 23 2026
So let me ask: is this related to the "fictitious pages" mentioned in D58320? If so, how is the LinuxKPI part to be written/work in the future world order with a real 'struct page'?
Oh, I wonder how you can trigger this from the semi-native driver? What was @gallatin 's error case?
You should add something like:
Originally reported (and tested with D57430): Mark Millard <marklmi@yahoo.com> (current@ July 25 2026)
Sep 22 2026
I have a full stack up for review for ages for PCI.
