All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the mm-hotfixes tree
Date: Mon, 5 Aug 2024 10:47:54 +0800	[thread overview]
Message-ID: <3507BDC6-16B2-4029-BF0A-9EBAFF6F91E8@linux.dev> (raw)
In-Reply-To: <20240805071723.571c7654@canb.auug.org.au>



> On Aug 5, 2024, at 05:17, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> In commit
> 
>  cbd28071cdab ("mm: list_lru: fix UAF for memory cgroup")
> 
> Fixes tag
> 
>  Fixes: 0a97c01cd20b ("list_lru: allow explicit memcg and NUMA node selection)
> 
> has these problem(s):
> 
>  - Subject has leading but no trailing quotes

Hi Stephen,

Thanks. In my v2, I've fixed this problem.

> 
> -- 
> Cheers,
> Stephen Rothwell


  reply	other threads:[~2024-08-05  2:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 21:17 linux-next: Fixes tag needs some work in the mm-hotfixes tree Stephen Rothwell
2024-08-05  2:47 ` Muchun Song [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-09  4:08 Stephen Rothwell
2025-09-10  7:32 Stephen Rothwell
2025-08-26  9:08 Stephen Rothwell
2025-08-20  4:50 Stephen Rothwell
2025-08-12  6:44 Stephen Rothwell
2025-08-12 13:46 ` Pasha Tatashin
2025-08-12 20:12   ` Andrew Morton
2024-10-07 20:44 Stephen Rothwell
2024-08-25 21:26 Stephen Rothwell
2024-07-02 22:09 Stephen Rothwell
2023-11-29 20:43 Stephen Rothwell
2023-11-30  1:07 ` Baoquan He
2023-06-07  4:35 Stephen Rothwell
2022-08-07 21:19 Stephen Rothwell
2022-08-07 23:01 ` Peter Xu
2022-04-27 22:36 Stephen Rothwell

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=3507BDC6-16B2-4029-BF0A-9EBAFF6F91E8@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.