public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-acpi@vger.kernel.org, James Morse <james.morse@arm.com>,
	loongarch@lists.linux.dev, linux-arch@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Ingo Molnar <mingo@redhat.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	jianyong.wu@arm.com, justin.he@arm.com,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Salil Mehta <salil.mehta@huawei.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH] cpu-hotplug: provide prototypes for arch CPU registration
Date: Wed, 11 Oct 2023 14:06:08 +0200	[thread overview]
Message-ID: <87o7h5l5xr.ffs@tglx> (raw)
In-Reply-To: <ZSV6i4pnjQqvWuKp@shell.armlinux.org.uk>

On Tue, Oct 10 2023 at 17:23, Russell King wrote:
> Okay, I give up. 15 days, still no real progress. I don't see any point
> in submitting any further patches for the kernel outside of those areas
> that I maintain. Clearly no one cares enough to bother (a) properly
> reviewing the patch, (b) applying the patch that Thomas thought
> "makes tons of sense."
>
> If patches that "makes tons of sense" just get ignored, then what does
> the future of the kernel hold? Crap, that's what, utter crap.
>
> As I said, it seems that the Linux kernel process is basically totally
> broken and rotten. If a six line patch that "makes tons of sense" can't
> be applied, then there's basically no hope what so ever.

Oh well. I usually try to keep track of such stuff, but this one fell
through the cracks.

Shit happens and we are all human, no?

Sorry for the wrong information about ia64. The removal did not happen
because someone stepped up as a possible maintainer.

Thanks,

        tglx

  reply	other threads:[~2023-10-11 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 16:28 [PATCH] cpu-hotplug: provide prototypes for arch CPU registration Russell King (Oracle)
2023-09-25 23:04 ` Gavin Shan
2023-09-25 23:17   ` Russell King (Oracle)
2023-10-03 14:34     ` Russell King (Oracle)
2023-10-03 17:37       ` Xin Li
2023-10-03 18:09         ` Russell King (Oracle)
2023-10-10 16:23 ` Russell King (Oracle)
2023-10-11 12:06   ` Thomas Gleixner [this message]
2023-10-11 13:08     ` Tomáš Glozar

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=87o7h5l5xr.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=jean-philippe@linaro.org \
    --cc=jianyong.wu@arm.com \
    --cc=justin.he@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=loongarch@lists.linux.dev \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=salil.mehta@huawei.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox