From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: EXPORT_SYMBOL_GPL_FOR_MODULES() heads up
Date: Mon, 23 Jun 2025 21:16:04 +0300 [thread overview]
Message-ID: <aFmZ5FRiNsoHtSPo@surfacebook.localdomain> (raw)
In-Reply-To: <20250623184158.28ebfef6@jic23-huawei>
Mon, Jun 23, 2025 at 06:41:58PM +0100, Jonathan Cameron kirjoitti:
> On Mon, 23 Jun 2025 13:45:07 +0300
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> > Pay attention to a new commit 707f853d7fa3 ("module: Provide
> > EXPORT_SYMBOL_GPL_FOR_MODULES() helper"). This one is what we
> > mostly need in IIO.
> >
>
> Thanks Andy - I'd not registered that merged.
>
> I was following the discussion that lead to that patch and
> it was targeted at a different use case to our typical one in IIO.
> I was to prevent anyone else getting access to a particular call
> that was needed for modular KVM. It's about abuse prevention rather
> than what we typically care about which is reducing namespace
> polution.
>
> Now that's not to say it isn't also helpful for us, but I'd like
> to not rush to using it until we see if it is getting general
> adoption outside of that specific KVM case and similar.
FWIW, I have noticed this due to the commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=b20d6576cdb3530d4a2d81611a8b8eb99780ce3e
> So let's wait a cycle or so and look again,
Sure.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-06-23 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 10:45 EXPORT_SYMBOL_GPL_FOR_MODULES() heads up Andy Shevchenko
2025-06-23 17:41 ` Jonathan Cameron
2025-06-23 18:16 ` Andy Shevchenko [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=aFmZ5FRiNsoHtSPo@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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