From: Thomas Gleixner <tglx@linutronix.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Len Brown <len.brown@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND][PATCH v2-resend] MAINTAINERS: mark simple firmware interface (SFI) obsolete
Date: Mon, 26 Aug 2019 17:12:12 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908261706460.1939@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190825173053.5649-1-lukas.bulwahn@gmail.com>
Lukas,
On Sun, 25 Aug 2019, Lukas Bulwahn wrote:
> Len Brown has not been active in this part since around 2010. The recent
> activity suggests that Thomas Gleixner and Jiang Lui were maintaining
> this part of the kernel sources. Jiang Lui has not been active in the
> kernel sources since beginning 2016. So, the maintainer's role seems to
> be now with Thomas.
Nice try. All I did there was converting the existing code to new
interfaces and to use SPDX identifiers. You touched it last, you own it, is
not really working.
TBH. I have no clue what that is except that it's bitrotting.
> SIMPLE FIRMWARE INTERFACE (SFI)
> -M: Len Brown <lenb@kernel.org>
> -L: sfi-devel@simplefirmware.org
> +M: Thomas Gleixner <tglx@linutronix.de>
> W: http://simplefirmware.org/
> -T: git git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-sfi-2.6.git
> -S: Supported
> +S: Obsolete
> F: arch/x86/platform/sfi/
> F: drivers/sfi/
> F: include/linux/sfi*.h
So why not removing this whole entry. arch/x86/platform/sfi is already
covered by x86 and the driver cruft falls back to the people who are used
to deal with dead drivers anyway.
Thanks,
tglx
next prev parent reply other threads:[~2019-08-26 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 17:30 Lukas Bulwahn
2019-08-26 15:12 ` Thomas Gleixner [this message]
2019-08-26 15:45 ` Lukas Bulwahn
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=alpine.DEB.2.21.1908261706460.1939@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=x86@kernel.org \
/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®