From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.1 final
Date: Sat, 10 Dec 2022 17:15:08 -0800 [thread overview]
Message-ID: <CAHk-=wgrapQ=pf0Btr9_0bso99E5Mq6FgANKLbN0mkdohfB4qQ@mail.gmail.com> (raw)
In-Reply-To: <20221210170317.130e7dbfc0e78de6067c4012@linux-foundation.org>
On Sat, Dec 10, 2022 at 5:03 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Tejun Heo (1):
> memcg: fix possible use-after-free in memcg_write_event_control()
Heh. Apparently your scripts to notice that some patch already made it
upstream didn't notice that I took this one directly already when it
was posted, so now it's duplicated.
Not a big deal.
Linus
next prev parent reply other threads:[~2022-12-11 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 1:03 Andrew Morton
2022-12-11 1:15 ` Linus Torvalds [this message]
2022-12-11 1:16 ` pr-tracker-bot
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='CAHk-=wgrapQ=pf0Btr9_0bso99E5Mq6FgANKLbN0mkdohfB4qQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox