From: Harry Yoo <harry@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
linux-kernel@vger.kernel.org, Hao Li <hao.li@linux.dev>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org
Subject: Re: [PATCH slab/for-next-fixes] MAINTAINERS: update slab.git URL
Date: Thu, 17 Sep 2026 19:47:25 +0100 [thread overview]
Message-ID: <aqwz4CrVP8sKDfn5@thinkstation> (raw)
In-Reply-To: <178965921180.1114058.11649457371183198247.b4-ty@b4>
On Thu, Sep 17, 2026 at 04:37:01PM +0100, Harry Yoo (Meta) wrote:
>
> On Thu, 17 Sep 2026 16:38:37 +0200, Vlastimil Babka (SUSE) wrote:
> > The slab.git tree has been moved to a new URL as part of the mm-next
> > integration. Reflect this in MAINTAINERS as well. The old URL will stay
> > around with historical branches and tags.
>
> Applied to mm/slab.git slab/for-next-fixes, thanks!
>
> [1/1] MAINTAINERS: update slab.git URL
> commit: 4c51f0b648cbf190d15d4ff60826c769f7e81df6
Haha, it took a while to figure out what `b4 -sl shazam` and `b4 ty -i`
actually do...
> https://git.kernel.org/pub/scm/linux/kernel/git/mm/slab.git/commit/?id=4c51f0b648cbf190d15d4ff60826c769f7e81df6
/me forgets and learns what `b4 trailers -u` does, once again
Now it has R-b from David Hildenbrand :-)
https://git.kernel.org/pub/scm/linux/kernel/git/mm/slab.git/commit/?id=f4feefcf46b9a63e4ab096c3f2cb260ef8e3902a
Whoa, looks like I didn't mess up something.
Thank you folks!
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-09-17 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 14:38 [PATCH slab/for-next-fixes] MAINTAINERS: update slab.git URL Vlastimil Babka (SUSE)
2026-09-17 15:30 ` David Hildenbrand (Arm)
2026-09-17 15:37 ` Harry Yoo (Meta)
2026-09-17 18:47 ` Harry Yoo [this message]
2026-09-18 2:31 ` SeongJae Park
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=aqwz4CrVP8sKDfn5@thinkstation \
--to=harry@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=david@kernel.org \
--cc=hao.li@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=vbabka@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 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.