Linux Power Management development
 help / color / mirror / Atom feed
From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Sasha Levin <sashal@kernel.org>
Cc: patches@lists.linux.dev,  stable@vger.kernel.org,
	 Mario Limonciello <mario.limonciello@amd.com>,
	 Nat Wittstock <nat@fardog.io>,
	 Lucian Langa <lucilanga@7pot.org>,
	 "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	rafael@kernel.org,  pavel@ucw.cz,  len.brown@intel.com,
	linux-pm@vger.kernel.org,  kexec@lists.infradead.org
Subject: Re: [PATCH AUTOSEL 6.15 6/8] PM: Restrict swap use to later in the suspend sequence
Date: Tue, 08 Jul 2025 16:46:19 -0500	[thread overview]
Message-ID: <87tt3mqrtg.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <aG2AcbhWmFwaHT6C@lappy> (Sasha Levin's message of "Tue, 8 Jul 2025 16:32:49 -0400")

Sasha Levin <sashal@kernel.org> writes:

> On Tue, Jul 08, 2025 at 02:32:02PM -0500, Eric W. Biederman wrote:
>>
>>Wow!
>>
>>Sasha I think an impersonator has gotten into your account, and
>>is just making nonsense up.
>
> https://lore.kernel.org/all/aDXQaq-bq5BMMlce@lappy/

It is nice it is giving explanations for it's backporting decisions.

It would be nicer if those explanations were clearly marked as
coming from a non-human agent, and did not read like a human being
impatient for a patch to be backported.

Further the machine given explanations were clearly wrong.  Do you have
plans to do anything about that?  Using very incorrect justifications
for backporting patches is scary.

I still highly recommend that you get your tool to not randomly
cut out bits from links it references, making them unfollowable.

>>At best all of this appears to be an effort to get someone else to
>>do necessary thinking for you.  As my time for kernel work is very
>>limited I expect I will auto-nack any such future attempts to outsource
>>someone else's thinking on me.
>
> I've gone ahead and added you to the list of people who AUTOSEL will
> skip, so no need to worry about wasting your time here.

Thank you for that.

I assume going forward that AUTOSEL will not consider any patches
involving the core kernel and the user/kernel ABI going forward.  The
areas I have been involved with over the years, and for which my review
might be interesting.

Eric

  parent reply	other threads:[~2025-07-08 21:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250708000215.793090-1-sashal@kernel.org>
2025-07-08  0:02 ` [PATCH AUTOSEL 6.15 6/8] PM: Restrict swap use to later in the suspend sequence Sasha Levin
2025-07-08  6:25   ` Pavel Machek
2025-07-08  6:39   ` Pavel Machek
2025-07-08 19:13   ` Eric W. Biederman
2025-07-08 19:32   ` Eric W. Biederman
2025-07-08 20:32     ` Sasha Levin
2025-07-08 20:37       ` Pavel Machek
2025-07-08 20:46         ` Willy Tarreau
2025-07-08 20:49           ` Pavel Machek
2025-07-08 21:12           ` Sasha Levin
2025-07-08 21:26             ` Pavel Machek
2025-07-09  5:34             ` Pavel Machek
2025-07-08 20:41       ` Pavel Machek
2025-07-08 21:46       ` Eric W. Biederman [this message]
2025-07-08 22:26         ` Sasha Levin
2025-07-09  5:39           ` Pavel Machek
2025-07-09 14:35             ` Mario Limonciello
2025-07-09 16:23           ` Eric W. Biederman
2025-07-09 16:35             ` Mario Limonciello
2025-07-09 16:55               ` Rafael J. Wysocki
2025-07-09 17:37             ` Sasha Levin
2025-07-08 20:38     ` Pavel Machek

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=87tt3mqrtg.fsf@email.froward.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=lucilanga@7pot.org \
    --cc=mario.limonciello@amd.com \
    --cc=nat@fardog.io \
    --cc=patches@lists.linux.dev \
    --cc=pavel@ucw.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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