[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a4e918c3-8d5c-9f89-903e-a34707cb6f0e@linux.intel.com>
Date: Mon, 16 Dec 2019 16:34:29 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: alsa-devel@...a-project.org, tiwai@...e.de,
linux-kernel@...r.kernel.org,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
vkoul@...nel.org, broonie@...nel.org,
srinivas.kandagatla@...aro.org, jank@...ence.com,
slawomir.blauciak@...el.com, Sanyog Kale <sanyog.r.kale@...el.com>,
Bard liao <yung-chuan.liao@...ux.intel.com>,
Rander Wang <rander.wang@...ux.intel.com>
Subject: Re: [alsa-devel] [PATCH v4 08/15] soundwire: add initial definitions
for sdw_master_device
>> No, I mean the new MODULE_NAMESPACE() support that is in the kernel.
>> I'll move the greybus code to use it too, but when you are adding new
>> apis, it just makes sense to use it then as well.
>
> ok, thanks for the pointer, will look into this.
This namespace check already saved me a lot of time. I found an issue in
our latest code (not submitted for review yet) with a new functionality
added to the wrong module and without the proper abstraction required...
Really nice tool, I can already see how useful it will be for on-going
code partitioning (SOF multi-client work and virtualization support).
Powered by blists - more mailing lists