From: "H. Peter Anvin" <hpa@zytor.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: David Rientjes <rientjes@google.com>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Dave Hansen <dave.hansen@intel.com>,
Andrey Panin <pazke@donpac.ru>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-visws-devel@lists.sf.net
Subject: Re: [patch 1/4] x86, apic: Only use default_wait_for_init_deassert
Date: Thu, 06 Feb 2014 14:57:44 -0800 [thread overview]
Message-ID: <52F41368.7060801@zytor.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402062342190.21991@ionos.tec.linutronix.de>
On 02/06/2014 02:52 PM, Thomas Gleixner wrote:
>>
>> I would love to see NumaQ, VisWS, Summit and ES7000 just nuked. In
>> fact, I'm thinking that unless someone steps up and explicitly claims
>> ownership of those platforms by adding their name to MAINTAINERS (or
>> reiterating them in the case of VisWS, which MAINTAINERS entry says "for
>> 2.6") we should just rip them all out.
>>
>> Anyone who wants to disagree?
>
> Anyone who disagrees is automatically appointed to fill in the vacancy
> in that section of the maintainers file:
>
> PALEONTOLOGICAL SYSTEMS
> M: vacant@paleontological.systems
> S: reanimation
>
... and *do the work*, too. Just having a MAINTAINERS entry isn't
enough, as we have seen many times in the past.
-hpa
next prev parent reply other threads:[~2014-02-06 22:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 7:54 [patch 1/4] x86, apic: Only use default_wait_for_init_deassert David Rientjes
2014-02-05 7:55 ` [patch 2/4] x86, apic: Switch wait_for_init_deassert to bool David Rientjes
2014-02-05 20:29 ` Thomas Gleixner
2014-02-10 13:31 ` [tip:x86/apic] x86/apic: Switch wait_for_init_deassert() to a bool flag tip-bot for David Rientjes
2014-02-05 7:55 ` [patch 3/4] x86, apic: Remove unused function prototypes David Rientjes
2014-02-05 20:31 ` Thomas Gleixner
2014-02-10 13:31 ` [tip:x86/apic] x86/apic: " tip-bot for David Rientjes
2014-02-05 7:55 ` [patch 4/4] x86, apic: Always define nox2apic and define it as initdata David Rientjes
2014-02-05 20:31 ` Thomas Gleixner
2014-02-10 13:31 ` [tip:x86/apic] x86/apic: " tip-bot for David Rientjes
2014-02-06 19:59 ` [patch 1/4] x86, apic: Only use default_wait_for_init_deassert Andi Kleen
2014-02-06 22:31 ` David Rientjes
2014-02-06 22:39 ` H. Peter Anvin
2014-02-06 22:52 ` Thomas Gleixner
2014-02-06 22:57 ` H. Peter Anvin [this message]
2014-02-06 22:58 ` Dave Hansen
2014-02-12 2:53 ` [GIT PULL] x86, apic: Remove support for Summit and ES7000 David Rientjes
2014-02-12 2:53 ` [patch 1/2] x86, apic: Remove support for ia32-based Unisys ES7000 David Rientjes
2014-02-12 2:53 ` [patch 2/2] x86, apic: Remove support for IBM Summit/EXA chipset David Rientjes
2014-02-12 4:29 ` [GIT PULL] x86, apic: Remove support for Summit and ES7000 H. Peter Anvin
2014-02-12 5:20 ` David Rientjes
2014-02-12 7:06 ` Ingo Molnar
2014-02-12 8:39 ` H. Peter Anvin
2014-02-12 12:50 ` Andi Kleen
2014-02-12 15:17 ` H. Peter Anvin
2014-02-10 13:31 ` [tip:x86/apic] x86/apic: Only use default_wait_for_init_deassert( ) tip-bot for David Rientjes
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=52F41368.7060801@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-visws-devel@lists.sf.net \
--cc=mingo@redhat.com \
--cc=pazke@donpac.ru \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.