From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kemeng Shi <shikemeng@huaweicloud.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH RESEND V2 0/5] Fixes and cleanups to xarray
Date: Mon, 11 Nov 2024 21:45:18 +0000 [thread overview]
Message-ID: <ZzJ67sFmZ7btTDfB@casper.infradead.org> (raw)
In-Reply-To: <20241111132816.3dcbb113241353e9a544adab@linux-foundation.org>
On Mon, Nov 11, 2024 at 01:28:16PM -0800, Andrew Morton wrote:
> On Tue, 12 Nov 2024 05:53:54 +0800 Kemeng Shi <shikemeng@huaweicloud.com> wrote:
>
> > This series contains some random fixes and cleanups to xarray. Patch 1-3
> > are fixes and patch 4-5 are cleanups. More details can be found in
> > respective patches.
>
> As we're at -rc7 I'm looking to stash low-priority things away for
> consideration after 6.13-r1.
>
> But I don't know if all of these are low-priority things. Because you
> didn't tell me!
I don't think any of them fix any bugs that any code currently in the
kernel would stumble across.
next prev parent reply other threads:[~2024-11-11 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 21:53 Kemeng Shi
2024-11-11 21:28 ` Andrew Morton
2024-11-11 21:45 ` Matthew Wilcox [this message]
2024-11-12 7:05 ` Kemeng Shi
2024-11-12 15:48 ` Matthew Wilcox
2024-11-13 1:25 ` Kemeng Shi
2024-11-11 21:53 ` [PATCH RESEND V2 1/5] Xarray: Do not return sibling entries from xas_find_marked() Kemeng Shi
2024-11-11 21:53 ` [PATCH RESEND V2 2/5] Xarray: distinguish large entries correctly in xas_split_alloc() Kemeng Shi
2024-11-11 21:53 ` [PATCH RESEND V2 3/5] Xarray: move forward index correctly in xas_pause() Kemeng Shi
2024-11-11 21:53 ` [PATCH RESEND V2 4/5] Xarray: remove repeat check in xas_squash_marks() Kemeng Shi
2024-11-11 21:53 ` [PATCH RESEND V2 5/5] Xarray: use xa_mark_t in xas_squash_marks() to keep code consistent Kemeng Shi
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=ZzJ67sFmZ7btTDfB@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shikemeng@huaweicloud.com \
/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