From: Paul Bolle <pebolle@tiscali.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: remove check for CONFIG_DEBUG_LL_SER3
Date: Tue, 04 Oct 2022 20:55:33 +0200 [thread overview]
Message-ID: <084a7aec62c8e1dc24633848d7114b45df785ea9.camel@tiscali.nl> (raw)
In-Reply-To: <CAMuHMdVwnJ-dG7eBY-BnH1aZQVxknnzr+zvoDr+53U8CE=NRiw@mail.gmail.com>
Geert Uytterhoeven schreef op di 04-10-2022 om 09:48 [+0200]:
> Arnd took it into soc/for-next as commit 4413794917ba3ff4 ("ARM:
> remove check for CONFIG_DEBUG_LL_SER3").
This is really nice!
One of the few of the commits that I'm actually proud of is e5a7286b5f1b
("x86, boot: Remove ancient, unconditionally #ifdef'd out dead code"). That
commit removed code that was dead for sixteen years. This patch - if it
crosses the finish line - will remove code that's been dead for twenty years.
Yay Geert! I'm so glad this patch was hibernated for eight years, promoting
code dead for twelve years to code dead for twenty years.
But there must be even older dead code in the tree. So let's make this a
contest! I'll ship some Dutch treats to the author of a patch that removes
code that has been dead for the longest time when committed by Linus no later
than December 5th, 2022. (Wikipedia can explain this odd deadline.)
Grave diggers: on your mark!
Paul Bolle
next prev parent reply other threads:[~2022-10-04 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:42 Geert Uytterhoeven
2022-10-04 7:44 ` Linus Walleij
2022-10-04 7:48 ` Geert Uytterhoeven
2022-10-04 18:55 ` Paul Bolle [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-14 8:12 Paul Bolle
2014-05-14 10:28 ` Arnd Bergmann
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=084a7aec62c8e1dc24633848d7114b45df785ea9.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rmk+kernel@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®