Messages in this thread | | | Subject | Re: [PATCH 0/3 v2] sh: fixes for various build and kconfig warnings | From | Rob Landley <> | Date | Sun, 12 Sep 2021 12:25:14 -0500 |
| |
On 9/12/21 5:36 AM, John Paul Adrian Glaubitz wrote: > Hi Rich! > > On 9/12/21 03:57, Rich Felker wrote: >> Hi. I see there's a situation that needs my attention here. I will >> plan to review and merge anything important/blocking that doesn't have >> problems this week. > > I'm glad to here that you're still active. I will try to help assembling > the list of patches. I won't be able to test them though as I'm not at > home so I'm unable to reset the machine in case it crashes due to a bad > kernel patch. So, basically, I just have one shot free.
I smoketest on qemu-system-sh4 first just because it's so convenient, then test on my j-core (sh2+) turtle board because it's the next most convenient thing (it's USB powered and one lives in my backpack).
>> At the same time, I am open to the possibility of a new maintainer or >> co-maintainer if that ends up being what makes sense. Are there any >> candidates? > > I would generally be interested to help although I'm not as knowledgeable > when it comes to low-level kernel development.
I'm in a similar position: I can put more cycles into this (and I've collected patch stacks for Rich before), but I don't have the domain expertise to make judgement calls about device tree representation, interrupt routing, nontrivial lock ordering, knowing when you need a memory barrier and why...
(Also, I've been running up to 3 days behind on my email recently, and catching up on weekends...)
Rob
| |