From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Cc: "Maciej W . Rozycki" <macro@orcam.me.uk>,
Tiezhu Yang <yangtiezhu@loongson.cn>, Willy Tarreau <w@1wt.eu>,
linux-edac@vger.kernel.org, linux-hams@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH 0/5] Remove dead linux-mips.org references
Date: Mon, 22 Feb 2021 17:19:00 +0100 [thread overview]
Message-ID: <20210222161905.1153-1-lukas.bulwahn@gmail.com> (raw)
Dear all,
The domain lookup for linux-mips.org fails for quite some time now.
Hence, webpages, the patchwork instance and Ralf Baechle's email there is
not reachable anymore.
First, I updated all sections in MAINTAINERS for references with linux-mips.org.
Then, I also quickly scanned through the whole git tree for linux-mips.org
references, and step-wise filtered out obvious copyright holder lines and
references to old email addresses.
git ls-files | xargs grep "linux-mips.org" | \
grep -v -i "Copyright" | grep -v -i "MODULE_AUTHOR" | grep -v -i "written" | \
grep -v "Ralf" | grep -v "Maciej" | grep -v "Yoichi" | grep -v "Ladislav"
I removed dead references or replaced them with their living counterparts if
available. However, these two cases remain and somebody might want to have a look:
1. case in ./arch/mips/include/asm/page.h:
<snip>
/*
* RELOC_HIDE was originally added by 6007b903dfe5f1d13e0c711ac2894bdd4a61b1ad
* (lmo) rsp. 8431fd094d625b94d364fe393076ccef88e6ce18 (kernel.org). The
* discussion can be found in
* https://lore.kernel.org/lkml/a2ebde260608230500o3407b108hc03debb9da6e62c@mail.gmail.com
*
* It is unclear if the misscompilations mentioned in
* https://lore.kernel.org/lkml/1281303490-390-1-git-send-email-namhyung@gmail.com
* also affect MIPS so we keep this one until GCC 3.x has been retired
* before we can apply https://patchwork.linux-mips.org/patch/1541/
*/
</snip>
Decision: Keep as is. Although GCC 3.x is long retired, it is unclear what
https://patchwork.linux-mips.org/patch/1541/ is and if it has been already
applied or not.
Question: does anyone know how to identify this patch?
2. case in ./drivers/parport/parport_ip32.c:
linux-mips.org tree is referred to in an old To do item:
<snip>
* To do:
*
* Fully implement ECP mode.
* EPP and ECP mode need to be tested. I currently do not own any
* peripheral supporting these extended mode, and cannot test them.
* If DMA mode works well, decide if support for PIO FIFO modes should be
* dropped.
* Use the io{read,write} family functions when they become available in
* the linux-mips.org tree. Note: the MIPS specific functions readsb()
* and writesb() are to be translated by ioread8_rep() and iowrite8_rep()
* respectively.
</snip>
Decision: Keep as is; anyone that wants to follow up on this will probably
understand that the reference is outdated anyway.
Please comment on these clean-up patches on this administrative topic.
Patch set applies cleanly on next-20210222.
Thanks,
Lukas
Lukas Bulwahn (5):
MAINTAINERS: mark sections from Ralf Baechle orphan
MAINTAINERS: remove linux-mips.org references
arch: mips: update references to current linux-mips list
arch: mips: remove dead references
MIPS: SGI-IP27: fix spelling in Copyright
MAINTAINERS | 20 ++++++--------------
arch/mips/Kconfig | 8 +-------
arch/mips/jazz/Kconfig | 12 +++---------
arch/mips/kernel/r4k-bugs64.c | 2 +-
arch/mips/lib/iomap-pci.c | 2 +-
arch/mips/sgi-ip27/ip27-timer.c | 4 ++--
arch/mips/sgi-ip32/ip32-irq.c | 2 +-
tools/include/nolibc/nolibc.h | 3 +--
8 files changed, 16 insertions(+), 37 deletions(-)
--
2.17.1
next reply other threads:[~2021-02-22 16:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 16:19 Lukas Bulwahn [this message]
2021-02-22 16:19 ` [PATCH 1/5] MAINTAINERS: mark sections from Ralf Baechle orphan Lukas Bulwahn
2021-02-22 16:19 ` [PATCH 2/5] MAINTAINERS: remove linux-mips.org references Lukas Bulwahn
2021-02-23 1:16 ` Huacai Chen
2021-02-23 9:48 ` Philippe Mathieu-Daudé
2021-02-26 8:29 ` Lukas Bulwahn
2021-02-22 16:19 ` [PATCH 3/5] arch: mips: update references to current linux-mips list Lukas Bulwahn
2021-02-23 1:17 ` Huacai Chen
2021-02-23 9:49 ` Philippe Mathieu-Daudé
2021-02-23 12:29 ` Thomas Bogendoerfer
2021-02-23 13:24 ` Maciej W. Rozycki
2021-02-22 16:19 ` [PATCH 4/5] arch: mips: remove dead references Lukas Bulwahn
2021-02-23 1:19 ` Huacai Chen
2021-02-23 9:59 ` Philippe Mathieu-Daudé
2021-02-23 12:30 ` Maciej W. Rozycki
2021-02-22 16:19 ` [PATCH 5/5] MIPS: SGI-IP27: fix spelling in Copyright Lukas Bulwahn
2021-02-23 1:20 ` Huacai Chen
2021-02-23 9:50 ` Philippe Mathieu-Daudé
2021-02-23 12:33 ` Maciej W. Rozycki
2021-02-23 13:33 ` Philippe Mathieu-Daudé
2021-02-23 13:25 ` Maciej W. Rozycki
2021-02-22 17:47 ` [PATCH 0/5] Remove dead linux-mips.org references Maciej W. Rozycki
2021-02-22 17:56 ` Lukas Bulwahn
2021-02-22 18:19 ` [EXTERNAL]Re: " Kurt Martin
2021-03-22 7:52 ` Lukas Bulwahn
[not found] ` <BY5PR22MB18410B38B795973450A10D4DC7659@BY5PR22MB1841.namprd22.prod.outlook.com>
2021-03-23 3:36 ` Kurt Martin
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=20210222161905.1153-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.de \
--cc=w@1wt.eu \
--cc=yangtiezhu@loongson.cn \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).