All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	David Hildenbrand <david@kernel.org>,
	 "Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	 Michal Hocko <mhocko@suse.com>, Jann Horn <jannh@google.com>,
	Pedro Falcato <pfalcato@suse.de>,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/3] remove mmap_action success, error hooks
Date: Fri, 22 May 2026 17:07:46 +0100	[thread overview]
Message-ID: <ahB-b2npY2_jICZU@lucifer> (raw)
In-Reply-To: <cover.1779462249.git.ljs@kernel.org>

FYI re: the sashiko reports on the v1:

https://sashiko.dev/#/patchset/cover.1779379804.git.ljs%40kernel.org

1. This was the bug the fix-patch fixed, it seems sashiko doesn't update when
   these are sent (which I cannot blame it for :).

   Anyway, I did say I felt fix-patches should just not be accepted any more to
   avoid various forms of confusion, so in future will just reply to ACK a
   thing like that, then send out a respin the next day :>)

2. The 'the series didn't introduce this' thread can just end right there ;)
   It's an existing behaviour that's been there from... very early on. It can
   wait. I will put it (probably quite far down) on my TODO to examine that.

Thanks, Lorenzo


      parent reply	other threads:[~2026-05-22 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 16:00 [PATCH v2 0/3] remove mmap_action success, error hooks Lorenzo Stoakes
2026-05-22 16:00 ` [PATCH v2 1/3] drivers/char/mem: eliminate unnecessary use of success_hook Lorenzo Stoakes
2026-06-01 15:18   ` David Hildenbrand (Arm)
2026-05-22 16:00 ` [PATCH v2 2/3] mm/vma: remove mmap_action->success_hook Lorenzo Stoakes
2026-06-01 15:19   ` David Hildenbrand (Arm)
2026-05-22 16:00 ` [PATCH v2 3/3] mm/vma: eliminate mmap_action->error_hook, introduce error_filter Lorenzo Stoakes
2026-06-01 15:25   ` David Hildenbrand (Arm)
2026-06-01 15:46     ` Lorenzo Stoakes
2026-06-02  9:16       ` David Hildenbrand (Arm)
2026-06-02 10:07         ` Lorenzo Stoakes
2026-06-02 11:23           ` David Hildenbrand (Arm)
2026-06-02 11:28             ` Lorenzo Stoakes
2026-05-22 16:07 ` Lorenzo Stoakes [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=ahB-b2npY2_jICZU@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=david@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=pfalcato@suse.de \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --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.