From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xu Yilun <yilun.xu@intel.com>
Cc: linux-kernel@vger.kernel.org, trix@redhat.com,
matthew.gerlach@linux.intel.com, russell.h.weight@intel.com,
lgoncalv@redhat.com, hao.wu@intel.com, mdf@kernel.org
Subject: Re: [PATCH v2] add the FPGA Device Feature List (DFL) EMIF support
Date: Sun, 20 Sep 2020 18:22:05 +0200 [thread overview]
Message-ID: <20200920162205.GA10210@kozik-lap> (raw)
In-Reply-To: <1600234622-8815-1-git-send-email-yilun.xu@intel.com>
On Wed, Sep 16, 2020 at 01:37:01PM +0800, Xu Yilun wrote:
> The patchsets "Modularization of DFL private feature drivers" & "add dfl
> bus support to MODULE_DEVICE_TABLE()" are all queued to linux-next. So
> there is no dependency now.
What do you mean there is no dependency? The DFL is required here and it
won't compile without these patches:
CC drivers/memory/dfl-emif.o
../drivers/memory/dfl-emif.c:10:10: fatal error: linux/fpga/dfl.h: No such file or directory
#include <linux/fpga/dfl.h>
^~~~~~~~~~~~~~~~~~
compilation terminated.
This simply cannot go in without dependency.
I described in your v1 submission what is needed here:
"Anyway I will need a stable tag with mentioned dependencies or this
will wait for the next cycle."
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-09-20 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 5:37 [PATCH v2] add the FPGA Device Feature List (DFL) EMIF support Xu Yilun
2020-09-16 5:37 ` [PATCH v2] memory: dfl-emif: add the DFL EMIF private feature driver Xu Yilun
2020-09-20 16:35 ` Krzysztof Kozlowski
2020-09-20 16:56 ` Krzysztof Kozlowski
2020-09-20 16:22 ` Krzysztof Kozlowski [this message]
2020-09-21 2:43 ` [PATCH v2] add the FPGA Device Feature List (DFL) EMIF support Xu Yilun
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=20200920162205.GA10210@kozik-lap \
--to=krzk@kernel.org \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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