From: Thorsten Blum <thorsten.blum@linux.dev>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: replace vmalloc + copy_from_user with vmemdup_user
Date: Wed, 24 Sep 2025 15:45:02 +0200 [thread overview]
Message-ID: <2B76A58C-8AE6-4DAF-9B6B-7927FB301F6B@linux.dev> (raw)
In-Reply-To: <CAKFNMonHxWSxW72Af8F_3Mhx39iO5hgVKAhTjpHVKsTBOQ-Z8g@mail.gmail.com>
Hi Ryusuke,
On 24. Sep 2025, at 14:18, Ryusuke Konishi wrote:
> ...
> So, rather than rushing it into the upcoming merge window, please let
> me schedule this to be sent upstream in the cycle after that.
Sounds good as this was meant for the next cycle anyway.
Thanks,
Thorsten
next prev parent reply other threads:[~2025-09-24 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 12:09 [PATCH] nilfs2: replace vmalloc + copy_from_user with vmemdup_user Thorsten Blum
2025-09-24 12:18 ` Ryusuke Konishi
2025-09-24 13:45 ` Thorsten Blum [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-30 15:46 Ryusuke Konishi
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=2B76A58C-8AE6-4DAF-9B6B-7927FB301F6B@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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;
as well as URLs for NNTP newsgroup(s).