From: Marc Zyngier <maz@kernel.org>
To: Martin Botka <martin.botka@somainline.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Alan Ma <tech@biqu3d.com>,
Luke Harrison <bttuniversity@biqu3d.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Martin Botka <martin@biqu3d.com>
Subject: Re: [PATCH] firmware: smccc: Export both soc_id functions
Date: Wed, 30 Aug 2023 15:00:07 +0100 [thread overview]
Message-ID: <8587262deb02cf46a922ec2ec3e647d5@kernel.org> (raw)
In-Reply-To: <20230830-smccc_export-v1-1-6ecc7661bc94@somainline.org>
On 2023-08-30 14:23, Martin Botka wrote:
> arm_smccc_get_soc_id_version and arm_smccc_get_soc_id_revision
> need to be exported so they can be used by modules.
> Currently sun50i cpu freq driver is planning to use these functions.
>
What for? I'm absolutely not keen on randomly exporting synbols
until we see what this is for.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-30 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 13:23 [PATCH] firmware: smccc: Export both soc_id functions Martin Botka
2023-08-30 14:00 ` Marc Zyngier [this message]
[not found] ` <CAPKp9ubXJbLQ_jOt3sp7Y8KXKyp42bzjHqbaa19LSqGMxE2yPg@mail.gmail.com>
2023-08-30 14:19 ` Martin Botka
2023-08-30 15:43 ` Sudeep Holla
2023-08-30 15:45 ` Martin Botka
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=8587262deb02cf46a922ec2ec3e647d5@kernel.org \
--to=maz@kernel.org \
--cc=andre.przywara@arm.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bttuniversity@biqu3d.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mark.rutland@arm.com \
--cc=martin.botka@somainline.org \
--cc=martin@biqu3d.com \
--cc=sudeep.holla@arm.com \
--cc=tech@biqu3d.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;
as well as URLs for NNTP newsgroup(s).