Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org
Subject: Re: mm.git review status at 7.2-rc7
Date: Fri, 14 Aug 2026 10:00:45 +0200	[thread overview]
Message-ID: <aef7eb6f-f7c9-44dc-9126-b70a38659e16@kernel.org> (raw)
In-Reply-To: <20260813141440.2010c9d9c34a24ae453a9ba4@linux-foundation.org>

On 8/13/26 23:14, Andrew Morton wrote:
> On Thu, 13 Aug 2026 00:46:45 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> 
>> On Wed, Aug 12, 2026 at 10:37:13AM +0200, David Hildenbrand (Arm) wrote:
>>>
>>> Oh, good, we fast-tracked an unreviewed cleanup as a stable fix upstream.
>>>
>>> What is happening.
> 
> Yes, the fix should have been tested, sent and merged as a standalone
> thing.  But I'm reluctant to split a series because that results in
> merging code which the author didn't test.
> 
>> Meanwhile a well-reviewed series which includes bugfixes is apparently
>> not even being considered for this merge window because I spent a lot of
>> time figuring out what Sashiko was concerned about?
>>
>> https://lore.kernel.org/linux-mm/20260805210557.1118966-1-willy@infradead.org/
>>
>> This was originally posted 5 weeks ago (ie when rc2 was current), so I
>> don't understand why it's not being considered.  It's been tested by the
>> people most likely to uncover bugs in it.  It's not going to get any
>> realistic testing in -next because most people use neither hugetlb nor
>> hwpoison.
> 
> Sorry, this simply fell through a crack.  Happens sometimes - poke me!
> 

Just noting that it's the right thing to do to not merge code without component
maintainer's ACKs :)

-- 
Cheers,

David


      reply	other threads:[~2026-08-14  8:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12  3:58 mm.git review status at 7.2-rc7 Andrew Morton
2026-08-12  4:04 ` Andrew Morton
2026-08-12  7:58 ` David Hildenbrand (Arm)
2026-08-12  8:37   ` David Hildenbrand (Arm)
2026-08-12 23:46     ` Matthew Wilcox
2026-08-13  7:16       ` David Hildenbrand (Arm)
2026-08-13 21:14       ` Andrew Morton
2026-08-14  8:00         ` David Hildenbrand (Arm) [this message]

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=aef7eb6f-f7c9-44dc-9126-b70a38659e16@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox