From: Ralf Baechle <firstname.lastname@example.org> To: Lukas Bulwahn <email@example.com> Cc: Thomas Bogendoerfer <firstname.lastname@example.org>, "open list:BROADCOM NVRAM DRIVER" <email@example.com>, "Maciej W . Rozycki" <firstname.lastname@example.org>, Tiezhu Yang <email@example.com>, Willy Tarreau <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, kernel-janitors <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org> Subject: Re: [PATCH v2 1/3] MAINTAINERS: mark sections from Ralf Baechle orphan Date: Sat, 17 Jul 2021 11:13:31 +0200 [thread overview] Message-ID: <YPKfO/d5rjG+C/fG@linux-mips.org> (raw) In-Reply-To: <CAKXUXMxFBaBneVZf3WCCYJ8Theu55Nf-gFe=hs5u3mMVd41mTw@mail.gmail.com> On Sat, Jul 17, 2021 at 09:03:05AM +0200, Lukas Bulwahn wrote: > So, given the feedback on this overall patch set from Maciej and Kurt: > - the domain lookup for linux-mips.org does resolve again. > - the patchwork instance moved. > - Ralf Baechle's email now does at least forward somewhere. Sorry, the site suffered a complete collapse after a hardware failure earlier this year - and I couldn't even get the failed drive replaced at the hoster as I didn't have the privilege of opening a ticket; that was only possible to the owner of the master account, a former MIPS employee who for health reasons no longer is with the company. The parent company of MIPS Wavecomp going through bankrupcy proceedings didn't help resolving the situation either. Anyway, there's progress on that front and I hope to get replacement hardware within the next week or so. The failed drive of the lmo server hardware changed its behavioud allowing me to reboot the system again on July 1st. I had given up on the old hardware in frustration so Kurt deserves the credits for getting me to try again. No data was lost in the crash itself. I'm now working on fixing all the failed subsystems, primarily due to a major OS upgrade by several releases, some old to-do list items and changes in the environment that affect the system. The time required to do so is enormous; I've done virtually nothing else since 1st of July. I've put an writeup about the system status to https://www.linux-mips.org/wiki/System_Recovery_Status which I'm keeping updated as work progresses. As for the MAINTAINERS for the ham radio protocols - AX.25 use is going down for many years and so is NET\ROM. ROSE has always been a very rare protocol but all three stacks still have active users. With that said, I doubt somebody to do active development and maintenace will be found. So maybe leave my name in but lower to "Odd Fixes" which has been the reality for years even before I took over and imho is how it should be continued. At this point my immediate priorities are the full restoration of the lmo server and after that linux-ax25.org will need TLC and I want those to be completed before diving into code again. Ralf
next prev parent reply other threads:[~2021-07-17 9:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-25 11:04 [PATCH v2 0/3] Remove dead linux-mips.org references Lukas Bulwahn 2021-06-25 11:04 ` [PATCH v2 1/3] MAINTAINERS: mark sections from Ralf Baechle orphan Lukas Bulwahn 2021-07-17 7:03 ` Lukas Bulwahn 2021-07-17 9:13 ` Ralf Baechle [this message] 2021-07-17 20:59 ` Joshua Kinard 2021-06-25 11:04 ` [PATCH v2 2/3] MAINTAINERS: remove linux-mips.org references Lukas Bulwahn 2021-06-25 11:04 ` [PATCH v2 3/3] arch: mips: remove dead references Lukas Bulwahn 2021-06-26 16:52 ` Philippe Mathieu-Daudé 2021-06-26 17:22 ` Maciej W. Rozycki 2021-07-17 6:53 ` Lukas Bulwahn 2021-07-17 6:52 ` Lukas Bulwahn 2021-06-25 15:49 ` [PATCH v2 0/3] Remove dead linux-mips.org references Maciej W. Rozycki 2021-06-26 23:45 ` Joe Perches 2021-06-28 1:28 ` Jiaxun Yang
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YPKfO/d5rjG+C/fG@linux-mips.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v2 1/3] MAINTAINERS: mark sections from Ralf Baechle orphan' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).