From: "Arnd Bergmann" <arnd@arndb.de>
To: "Frank Li" <Frank.li@nxp.com>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Vinod Koul" <vkoul@kernel.org>, "Peng Fan" <peng.fan@nxp.com>,
"Fabio Estevam" <festevam@denx.de>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH] dmaengine: fsl-edma: fix Makefile logic
Date: Thu, 11 Jan 2024 17:23:03 +0100 [thread overview]
Message-ID: <5d2d8e57-0041-40af-b237-05f3275008bd@app.fastmail.com> (raw)
In-Reply-To: <ZaASsqnq5ZYdcjm6@lizhi-Precision-Tower-5810>
On Thu, Jan 11, 2024, at 17:09, Frank Li wrote:
> On Thu, Jan 11, 2024 at 07:23:34AM +0100, Arnd Bergmann wrote:
>> On Thu, Jan 11, 2024, at 01:02, Frank Li wrote:
>
> It should be better link into same module because some debugfs and trace
> improvement are on my TODO list. Export symbols will make more unnessary
> complex.
Ok, I'll see what I can come up with
> Or simple exclude MCF_EDMA by change Kconfig
>
> config MCF_EDMA
> tristate "Freescale eDMA engine support, ColdFire mcf5441x SoCs"
> depends on !FSL_EDMA
> ^^^^^
> depends on M5441x || COMPILE_TEST
This does not actually prevent building both as modules, it
only enforces that you can't have them both enabled if one
of them is built-in.
Arnd
next prev parent reply other threads:[~2024-01-11 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 23:03 [PATCH] dmaengine: fsl-edma: fix Makefile logic Arnd Bergmann
2024-01-11 0:02 ` Frank Li
2024-01-11 6:23 ` Arnd Bergmann
2024-01-11 16:09 ` Frank Li
2024-01-11 16:23 ` Arnd Bergmann [this message]
2024-01-11 23:45 ` kernel test robot
2024-01-12 7:50 ` kernel test robot
2024-01-22 11:27 ` Vinod Koul
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=5d2d8e57-0041-40af-b237-05f3275008bd@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Frank.li@nxp.com \
--cc=arnd@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=festevam@denx.de \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=vkoul@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