All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: shao.mingyin@zte.com.cn, akpm@linux-foundation.org,
	linux-mm@kvack.org,  virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/balloon: fix NR_BALLOON_PAGES accounting on migration failure
Date: Fri, 20 Nov 2026 10:36:35 +0000	[thread overview]
Message-ID: <awAijOul2KPFT1CQ@lucifer> (raw)
In-Reply-To: <96462da9-9437-4774-a5c7-f99858481ece@kernel.org>

On Fri, Nov 20, 2026 at 10:59:47AM +0100, David Hildenbrand (Arm) wrote:
> On 11/14/26 18:31, Lorenzo Stoakes (ARM) wrote:
> > NAK.
> >
> > this is generated by some AI slopper's script, spamming the kernel. The
> > patches I looked at were wrong/broken, so no to anything from this person.
> >
> > They've sent 300 mails in under four weeks spanniing: ata, scsi, target,
> > ufs, nvme/nvmet, ubifs, ublk, zloop, dm, md, mmc, virtio-blk, mfd, gpio,
> > pwm, spi, PCI, ASoC, ACPI, net, vfs mount, block partitions, and now mm.
> >
> > and 17 series across 7 subsystems over the past 23 hours.
> >
> > We need a way to ban emails from people like this...
>
> Yeah, that's absolutely annoying. In particular as we REQUIRE people to
> understand the changes they submit, and own the code.
>
> That clearly won't happen in this case.
>
> There is a real (low prio) bug hiding in there, so something to be fixed. I'll
> take care of it.
>
> I'll take care of it.

Ack, yeah, I think the best approach is to treat these as reports, and if
there's anything valid pull that out for a member of the core team :)

--
Cheers, Lorenzo

  reply	other threads:[~2026-11-20 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 16:47 [PATCH] mm/balloon: fix NR_BALLOON_PAGES accounting on migration failure shao.mingyin
2026-11-14 17:31 ` Lorenzo Stoakes (ARM)
2026-11-20  9:59   ` David Hildenbrand (Arm)
2026-11-20 10:36     ` Lorenzo Stoakes (ARM) [this message]
2026-11-15 16:47 ` sashiko-bot

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=awAijOul2KPFT1CQ@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shao.mingyin@zte.com.cn \
    --cc=virtualization@lists.linux.dev \
    /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.