On Tue, Mar 18, 2025 at 11:14 AM Johannes Berg
wrote:
>
> The list is fine, but the patch wasn't even CC'ed there, so we don't
> have it in our patchwork:
> https://patchwork.ozlabs.org/project/linux-um/list/
Ah, right, David added it.
> I was just picking up um patches, but given that it was a
On Tue, 2025-03-18 at 11:10 +0100, Miguel Ojeda wrote:
> On Tue, Mar 18, 2025 at 9:07 AM David Gow wrote:
> >
> > Is there anything holding this up for the upcoming merge window?
> >
> > Miguel: I'm assuming you'd rather take this (and possibly [1] as well)
> > via Rust, but if it goes in via th
On Tue, Mar 18, 2025 at 9:07 AM David Gow wrote:
>
> Is there anything holding this up for the upcoming merge window?
>
> Miguel: I'm assuming you'd rather take this (and possibly [1] as well)
> via Rust, but if it goes in via the uml tree, that'd be fine by me,
> too.
We try to get arch maintain
On Sat, 8 Feb 2025 at 21:32, Thomas Weißschuh wrote:
>
> Usermode Linux uses "um" as primary architecture name and the underlying
> physical architecture is provided in "SUBARCH".
> Resolve the target architecture flags through that underlying architecture.
> This is the same pattern as used by sc
On Sat, 8 Feb 2025 at 21:32, Thomas Weißschuh wrote:
>
> Usermode Linux uses "um" as primary architecture name and the underlying
> physical architecture is provided in "SUBARCH".
> Resolve the target architecture flags through that underlying architecture.
> This is the same pattern as used by sc
