From: Moritz Fischer <mdf@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Xu Yilun <yilun.xu@intel.com>,
mdf@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org, trix@redhat.com,
lgoncalv@redhat.com, Russ Weight <russell.h.weight@intel.com>
Subject: Re: [PATCH v3] memory: dfl-emif: add the DFL EMIF private feature driver
Date: Mon, 21 Sep 2020 13:31:04 -0700 [thread overview]
Message-ID: <20200921203104.GA35580@epycbox.lan> (raw)
In-Reply-To: <20200921072311.GA6133@kozik-lap>
Hi Krzysztof,
On Mon, Sep 21, 2020 at 09:23:11AM +0200, Krzysztof Kozlowski wrote:
> On Mon, Sep 21, 2020 at 01:31:20PM +0800, Xu Yilun wrote:
> > This driver is for the EMIF private feature implemented under FPGA
> > Device Feature List (DFL) framework. It is used to expose memory
> > interface status information as well as memory clearing control.
> >
> > The purpose of memory clearing block is to zero out all private memory
> > when FPGA is to be reprogrammed. This gives users a reliable method to
> > prevent potential data leakage.
> >
> > Signed-off-by: Xu Yilun <yilun.xu@intel.com>
> > Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> > ---
> > v2: Adjust the position of this driver in Kconfig.
> > Improves the name of the Kconfig option.
> > Change the include dfl-bus.h to dfl.h, cause the previous patchset
> > renames the file.
> > Some minor fixes and comment improvement.
> > v3: Adjust the position of the driver in Makefile.
> > ---
> > .../ABI/testing/sysfs-bus-dfl-devices-emif | 25 +++
> > drivers/memory/Kconfig | 9 +
> > drivers/memory/Makefile | 2 +
> > drivers/memory/dfl-emif.c | 207 +++++++++++++++++++++
> > 4 files changed, 243 insertions(+)
> > create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl-devices-emif
> > create mode 100644 drivers/memory/dfl-emif.c
> >
>
> Hi Moritz,
>
> Since this depends on dfl patches, I would need a stable tag with them
> or you can take it directly:
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> Best regards,
> Krzysztof
The FPGA patches go through Greg's tree. For the time being it's
probably easiest if I take the changes through my tree once Greg pulled
my tree.
Do you have any feedback to better handle this sort of subsystem
spanning changesets for me?
Thanks,
Moritz
next prev parent reply other threads:[~2020-09-21 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 5:31 [PATCH v3] add the FPGA Device Feature List (DFL) EMIF support Xu Yilun
2020-09-21 5:31 ` [PATCH v3] memory: dfl-emif: add the DFL EMIF private feature driver Xu Yilun
2020-09-21 7:23 ` Krzysztof Kozlowski
2020-09-21 20:31 ` Moritz Fischer [this message]
2020-09-21 20:46 ` Krzysztof Kozlowski
2020-09-22 3:17 ` Moritz Fischer
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=20200921203104.GA35580@epycbox.lan \
--to=mdf@kernel.org \
--cc=krzk@kernel.org \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).