From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andy Shevchenko" <andy.shevchenko@gmail.com>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Daniel Scally" <djrscally@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: int3472: make common part a separate module
Date: Wed, 29 May 2024 16:48:26 +0200 [thread overview]
Message-ID: <3fa493d3-51bb-48bf-b91f-57493be23937@app.fastmail.com> (raw)
In-Reply-To: <CAHp75VcVdwxv5Mm3GEv7SmsCiN3ZACpejNb7V_Ld1NBTxcXixQ@mail.gmail.com>
On Wed, May 29, 2024, at 16:28, Andy Shevchenko wrote:
> On Wed, May 29, 2024 at 5:14 PM Arnd Bergmann <arnd@arndb.de> wrote:
>> On Wed, May 29, 2024, at 15:41, Andy Shevchenko wrote:
>> > On Wed, May 29, 2024 at 12:50 PM Arnd Bergmann <arnd@kernel.org>
> It's different from the exported namespace.
> The function prefixes are needed due to C language, as we can't have
> two functions named the same. The export OTOH is what used for linking
> modules and if there is no need to have it exported globally, if, for
> example, compiling in this one.
>
> So, can we move to the exported namespace at the same time?
Maybe you can come up with a patch then? I have no idea
which namespace to use here, seeing that there are already
six differnet namespaces in use in drivers/platform/x86/intel/
but none of them seem to be a good fit for this one.
Are you asking to just define another namespace here?
How would I define what the rules about using this namespace
are, and where are they documented?
Arnd
next prev parent reply other threads:[~2024-05-29 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 9:49 Arnd Bergmann
2024-05-29 13:41 ` Andy Shevchenko
2024-05-29 14:13 ` Arnd Bergmann
2024-05-29 14:28 ` Andy Shevchenko
2024-05-29 14:48 ` Arnd Bergmann [this message]
2024-05-29 14:53 ` Andy Shevchenko
2024-08-05 15:02 ` Hans de Goede
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=3fa493d3-51bb-48bf-b91f-57493be23937@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@kernel.org \
--cc=djrscally@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®