All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: sashiko-reviews@lists.linux.dev
Cc: sashiko-bot@kernel.org,
	Matthew Wilcox (Oracle) <willy@infradead.org>,
	linux-mm@kvack.org,
	"Shardul Bankar" <shardul.b@mpiricsoftware.com>,
	David Hildenbrand (ARM) <david@kernel.org>,
	"Dev Jain" <dev.jain@arm.com>,
	janak@mpiricsoftware.com, "Jinjiang Tu" <tujinjiang@huawei.com>
Subject: Re: [PATCH 1/2] lib: xarray: free unused spare node in xas_create_range()
Date: Sun, 15 Nov 2026 19:59:09 -0800	[thread overview]
Message-ID: <20261115195909.b91edf975dee06ce566e3437@linux-foundation.org> (raw)
In-Reply-To: <sashiko-outbox-216113@kernel.org>

On Mon, 16 Nov 2026 03:17:13 +0000 sashiko-bot@kernel.org wrote:

> [ nag nag nag ]

bah.

> [Severity: Low]
> Is the Fixes tag pointing to the right commit?

OK, let's make it

	Fixes: 77da9389b9d5 ("mm: Convert collapse_shmem to XArray")

it doesn't have cc:stable anyway, but afaik lib/ is subject to
-stable's blanket "backport everything which has Fixes:" rule.

So I'll also add

	Cc: <stable+noautosel@kernel.org> # not harmful enough to bother

unless people disagree?


  reply	other threads:[~2026-11-16  3:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15  3:16 [PATCH 0/2] xarray: free unused spare node after range creation Andrew Morton
2026-11-15  3:16 ` [PATCH 1/2] lib: xarray: free unused spare node in xas_create_range() Andrew Morton
2026-11-16  3:17   ` sashiko-bot
2026-11-16  3:59     ` Andrew Morton [this message]
2026-11-15  3:16 ` [PATCH 2/2] lib/test_xarray: check unused spare node after range creation Andrew Morton

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=20261115195909.b91edf975dee06ce566e3437@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=janak@mpiricsoftware.com \
    --cc=linux-mm@kvack.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=shardul.b@mpiricsoftware.com \
    --cc=tujinjiang@huawei.com \
    --cc=willy@infradead.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.