From: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Marco Elver <elver@google.com>, Arnd Bergmann <arnd@kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: export copy_to_kernel_nofault
Date: Sun, 22 Jun 2025 10:23:30 +0500 [thread overview]
Message-ID: <CACzwLxjW+y=r1b0RiLB-qCEzSuoA4K1V80=Qyxhnhm0GX7-Svg@mail.gmail.com> (raw)
In-Reply-To: <20241107142938.c38ce0a63add88af49216b2f@linux-foundation.org>
On Fri, Nov 8, 2024 at 3:29 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Wed, 23 Oct 2024 00:05:36 -0700 Christoph Hellwig <hch@infradead.org> wrote:
>
> > On Wed, Oct 23, 2024 at 09:02:23AM +0200, Marco Elver wrote:
> > > Another alternative is to just #ifndef MODULE the offending test case,
> > > so it's only available if built-in. No need to just make the whole
> > > test built-in only. I know there are users of this particular test
> > > that rely on it being a module.
> >
> > That sounds good to me.
>
> We still don't have patch which does this, so this series is stalled.
>
> Sabyrzhan, could you please consider this?
I've just posted a follow-up that removes the exported symbol.
See Message-Id: <20250622051906.67374-1-snovitoll@gmail.com>
Sorry for taking so long.
prev parent reply other threads:[~2025-06-22 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:11 Arnd Bergmann
2024-10-18 15:12 ` David Hildenbrand
2024-10-18 15:35 ` Andrey Konovalov
2024-10-23 6:53 ` Christoph Hellwig
2024-10-23 6:57 ` Marco Elver
2024-10-23 6:59 ` Christoph Hellwig
2024-10-23 7:02 ` Marco Elver
2024-10-23 7:05 ` Christoph Hellwig
2024-11-07 22:29 ` Andrew Morton
2025-06-22 5:23 ` Sabyrzhan Tasbolatov [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='CACzwLxjW+y=r1b0RiLB-qCEzSuoA4K1V80=Qyxhnhm0GX7-Svg@mail.gmail.com' \
--to=snovitoll@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=elver@google.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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