#
✕ nick:arnd
#asahi-dev · 2026-04-13 19:41
arndsven: send it as fixes now, so we can still decide whether to apply it before or after rc1
#asahi-dev · 2025-03-09 11:39
arndsven: my tree is based on -rc3, so you can send a patch based on that if that helps, or I can merge it into the fixes branch
#asahi-dev · 2025-02-08 14:19
arndI might change the subject line to s/myself/Janne/ since that makes more sense for the shortlog
#asahi-dev · 2025-02-08 14:17
arndI usually pick up updates to MAINTAINERS in the bugfix branch since it helps to have the latest version in the release, and there is no regression risk
#asahi-dev · 2025-02-08 14:16
arndfor the maintainer file update, neither of those is important
#asahi-dev · 2025-02-08 14:16
arndin general, patches and pull requests sent to soc@lists.linux.dev are equivalent for simple changes, while for any larger series a pull request is nicer because it gives you the chance to have a summary for the merge commit that gets preserved in the git history, and you can be sure I get the exact same commit IDs that you have tested
#asahi-dev · 2025-02-08 14:13
arndsven: the patch to soc@ is sufficient, you can see it's in patchwork at https://patchwork.kernel.org/project/linux-soc/list/ so I will pick it up from there
#asahi-dev · 2024-04-20 20:47
arndjannau: only in the sense that it seemed easier than renaming the files again or having a multi-object file with a single object in it. Usually the name doesn't matter much since it just gets autoloaded, but feel free to change the name back if that helps you
#asahi-dev · 2023-05-11 06:17
arndmarcan: sorry, I ended up not having a chance to talk to jassi, saw him from a distance a few times. If you have a branch ready for the change, please send it to me soon and put him on Cc to give him enough time for a nak if he still has concerns
#asahi-dev · 2023-04-27 09:28
arndmarcan: I'm at Linaro Connect right now, I think jassi is here as well, will ask him about it if I see him
#asahi-dev · 2023-03-10 16:28
arndjannau: I had some problems with it a while ago and still use ethernet in my USB hub. It probably works, but not using the pci patches helped reduce the number of branches I had to merge
#asahi-dev · 2023-03-10 16:26
arndthanks jannau, I think that's all I need, I don't actually use pcie or wlan, just nvme and dcp
#asahi-dev · 2023-03-10 14:19
arndI did not try to rebase the gpu branch
#asahi-dev · 2023-03-10 14:18
arndmaz: I tried but ran into problems rebasing the t6000-dart branch on top of what was already merged and broke dcp in the process, so I went back to 6.2 plus selected branches. I think all the other branches I use were trivial to merge with or rebased on top of 6.3-rc1.
#asahi-dev · 2023-02-14 12:13
arndmarcan: it's really late for new content for 6.3, I would much prefer to have an intitial to merge by -rc4 rather than -rc8, with follow-up patches and fixes on top up to the merge window. I have a few other things going on this week, so it's possible that this will have to wait for 6.4, but I'll have a look when you send it
#asahi-dev · 2023-02-14 11:55
arndI don't have any other fixes queued at the moment though, and it's probably not urgent enough to send it to linus if it's the only other thing
#asahi-dev · 2023-02-14 11:53
arndmarcan: yes, that should be fine. I tend to fast-track MAINTAINERS file updates through the fixes branch, so if you do the move now and I end up sending another fixes PR, it would be reflected in 6.2
#asahi-dev · 2023-02-10 08:08
arndI usually tell driver writers to avoid __packed annotations because it makes accesses more expensive when the structure is known to be aligned, but here is sounds like the right thing to do
#asahi-dev · 2023-02-10 08:07
arndlina: actually just marking the structures as __packed (with a comment) should be sufficient to make the compiler do the right thing for unaligned access on all theoretical target architectures
#asahi-dev · 2023-02-10 07:14
arndlina: ah, makes sense. Accessing the pointer would be good I think. Maybe use get_unaligned() for reading the data then, it's only a few words anyway so it shouldn't clutter up the code too much, and it will document why it's done
#asahi-dev · 2023-02-09 20:28
arndwhat is the purpose of the memcpy() to a local structure, can this just access the original data instead?
#asahi-dev · 2023-02-09 20:26
arndthe 1024 byte limit is only on 32-bit architectures, so a 'depends on 64BIT' would avoid that for compile testing, but ideally it should not use that much stack
#asahi-dev · 2023-02-09 20:25
arndlina: my randconfig build setup has a lot of randconfig warnings "drivers/soc/apple/rtkit-crashlog.c:127:6: error: stack frame size (1048) exceeds limit (1024) in 'apple_rtkit_crashlog_dump_regs' [-Werror,-Wframe-larger-than]" from commit 22991d8d5725 ("soc: apple: rtkit: Add register dump decoding to crashlog")
#asahi-dev · 2023-02-01 19:43
arndsven: let me know if you'd like me to try my OWCTB3ENVXP00 disk enclosure, or if you'd like to use it for testing yourself.
#asahi-dev · 2023-01-13 12:25
arndchadmed_: it would help to have the actual specification, but the thing I can tell for sure is that at the moment every Intel Socket1700 mainboard advertises TB4, while the AMD AM5 boards only advertise USB4, see https://www.asus.com/motherboards-components/motherboards/proart/proart-x670e-creator-wifi/techspec/
#asahi-dev · 2023-01-13 12:09
arndhttps://www.thunderbolttechnology.net/sites/default/files/intel-thunderbolt4-announcement-press-deck.pdf seems very explicit about requiring "Intel® Virtualization Technology for Directed I/O" rather than any other way of doing the same thing
#asahi-dev · 2023-01-13 12:09
arndmarcan: I think for all practical purposes the requirement is being either Intel or Apple.
#asahi-dev · 2023-01-13 11:15
arndBut I think that also rules out M1 because of DART, unless they actually made that compatible with Intel's IOMMU
#asahi-dev · 2023-01-13 11:14
arndmarcan, sven: regarding tb4 spec compliance, it sounds to me like Intel intentionally picked VT-D as a requirement in order to exclude AMD cpus
#asahi-dev · 2022-10-05 09:46
arndmaybe send the stuff that you already have right after doing the rebase and some testing, and then base any other material you want in 6.2 on top of that branch. There is no problem sending multiple pull requests for a given release, and I always prefer getting the bulk of the patches as early as possible to have less regression potential late in the cycle
#asahi-dev · 2022-10-05 09:44
arndmarcan: right. Please rebase on top of v6.1-rc1 once that is released
#asahi-dev · 2022-09-22 14:19
arndmost trees have some variant of "for-next" and an an additional "fixes" branch, with the latter being for stuff that should get in before the merge window but could also benefit from linux-next testing
#asahi-dev · 2022-09-22 14:18
arndyes, that also documents nicely what you plan to send me, which can come in handy when I look at the contents early, or for other folks that are interested
#asahi-dev · 2022-09-22 14:16
arndmost platform maintainers have their tree added to linux-next, which gives a little wider CI testing from all the bots before I pull the contents
#asahi-dev · 2022-09-22 14:15
arndah, I see. You may want to email Stephen Rothwell <sfr@canb.auug.org.au> cc lkml then to give a URL to add to linux-next.
#asahi-dev · 2022-09-22 14:13
arndmarcan: is it in linux-next already?
#asahi-dev · 2022-09-22 14:12
arndmarcan: I still have a bit of a backlog to handle first, no need to send it right away
#asahi-dev · 2022-09-22 13:11
arndideally you should try to do the binding changes before code changes in another branch, so you can just merge in the binding commits (on top of rc1) into the dts branch
#asahi-dev · 2022-09-22 13:08
arndI sometimes merge in smaller dependencies outside of arch/*/boots/dts/* when there is a strong reason, but otherwise try to keep the arm/dt branch having only dt changes to ensure that there are no incompatible binding changes
#asahi-dev · 2022-09-22 13:06
arndmarcan: I'll take the branch without the binding patch then. The warning does not show up in a plain allmodconfig build, and the driver change is a bit larger than what I'm comfortable with having in the dt branch
#asahi-dev · 2022-09-22 12:46
arndis the binding the first one?
#asahi-dev · 2022-09-22 12:45
arndmarcan: I'm confused now, which binding patch is this? I don't want to merge large chunks of the asoc tree, so rebasing on top of that would not work unless the patches are right on top of rc1
#asahi-dev · 2022-09-17 18:09
arndmarcan, rmk: applied the apple_rtkit_poll() patch directly from the list now, no need to resend
#asahi-dev · 2022-09-17 18:07
arnd6.0-rc1 through rc3 were broken, 5.19 should be fine
#asahi-dev · 2022-09-17 18:06
arndwell, not sure if you hit the same thing, but multiple people were affected by a change in the driver core that resulted in deferred probe issues and got reverted in -rc4
#asahi-dev · 2022-09-17 18:05
arndthe deferred probe bug should be fixed in -rc4
#asahi-dev · 2022-09-17 17:27
arndj`ey: yes, I saw the submission, I'm just waiting for marcan to pick them up and send me a pull request to forward to torvalds
#asahi-dev · 2022-09-17 17:24
arndIt would be good to have a PR for the t6000 dts files though
#asahi-dev · 2022-09-17 17:23
arndmarcan: do you have pull requests for 6.1 lined up that you want in the soc tree? rmk asked about https://lore.kernel.org/linux-arm-kernel/E1oYNqp-006lXn-Hu@rmk-PC.armlinux.org.uk/, which I can pick up directly if you have no other code changes
#asahi-dev · 2022-09-13 16:17
arndrmk: yes, I usually keep those in a separate branch

plus ›