linux-kernel - Re: memblock: updates for 6.12-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHk-=wh=8JhAWjaxZPEOQgarTTsqPV0AQO=Q0USYtG009EYhUA@mail.gmail.com>
Date: Wed, 25 Sep 2024 11:50:10 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Mike Rapoport <rppt@...nel.org>
Cc: Alexander Gordeev <agordeev@...ux.ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, 
	Christian Brauner <brauner@...nel.org>, David Hildenbrand <david@...hat.com>, 
	Gerald Schaefer <gerald.schaefer@...ux.ibm.com>, Heiko Carstens <hca@...ux.ibm.com>, 
	"Liam R . Howlett" <Liam.Howlett@...cle.com>, Matthew Wilcox <willy@...radead.org>, 
	Oleg Nesterov <oleg@...hat.com>, Vasily Gorbik <gor@...ux.ibm.com>, 
	Wei Yang <richard.weiyang@...il.com>, linux-kernel@...r.kernel.org, 
	linux-mm@...ck.org, linux-s390@...r.kernel.org
Subject: Re: memblock: updates for 6.12-rc1

On Sun, 22 Sept 2024 at 23:37, Mike Rapoport <rppt@...nel.org> wrote:
>
> memblock: updates for 6.12-rc1

Please make sure that there is a "git pull" somewhere in your pull request.

Now, the "git" part will always be there from a git request-pull (as
part of the "are available in the Git repository at" string), but I do
want to see a "pull" somewhere too. Otherwise my search functions
don't light up the email, and then it takes me longer to notice.

Most people put "[GIT PULL]" in the subject line, since that's also
how you get the attention of the pr-tracker-bot. So that's the
suggested way to do it, even if my search functionality is a lot more
permissive and just wants to see "git" and "pull" _somewhere_ in the
email.

You have done that in the past, I'm not sure why it didn't happen this time.

               Linus