[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE_wzQ_DTnrU9QbADZuNyt4fszAiTwa04D9muC-xE_S3MM9eGQ@mail.gmail.com>
Date: Wed, 5 Jan 2022 14:50:19 -0800
From: Dmitry Torokhov <dtor@...omium.org>
To: Gwendal Grignou <gwendal@...omium.org>
Cc: bleung@...omium.org, groeck@...omium.org, myungjoo.ham@...sung.com,
cw00.choi@...sung.com, benjamin.tissoires@...hat.com,
jic23@...nel.org, hverkuil-cisco@...all.nl, mchehab@...nel.org,
lee.jones@...aro.org, pmalani@...omium.org, sre@...nel.org,
thierry.reding@...il.com, u.kleine-koenig@...gutronix.de,
lgirdwood@...il.com, a.zummo@...ertech.it, cychiang@...omium.org,
perex@...ex.cz, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/17] Add export symbol namespace PL_CHROMEOS
Hi Gwendal,
On Wed, Jan 5, 2022 at 2:07 PM Gwendal Grignou <gwendal@...omium.org> wrote:
>
> Add a symbol namespace for functions exported by the plaform chromeos
> subsystem.
It would be great to explain why this is needed/desirable. What are
the benefits of introducing this namespace? What problem are you
trying to solve?
> Add depenencies for all drivers using these function.
>
> 'make nsdeps' is used to fix the dependencies.
>
> Signed-off-by: Gwendal Grignou <gwendal@...omium.org>
>
> Gwendal Grignou (17):
> plaform: chrome: Add PL_CHROMEOS export symbol namespace
> iio:cros_ec_sensors: Add PL_CHROMEOS dependency
I wonder if ordering patches this way breaks compilation (patches
should be structured in such a way that one need not apply entire
series to get to buildable kernel). Isn't putting symbols into new
namespace makes them unavailable to modules unless they explicitly
import it?
Thanks.
--
Dmitry
Powered by blists - more mailing lists