linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xu Yilun <yilun.xu@intel.com>
Cc: mdf@kernel.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	trix@redhat.com, lgoncalv@redhat.com, hao.wu@intel.com,
	Russ Weight <russell.h.weight@intel.com>
Subject: Re: [PATCH v11 2/2] memory: dfl-emif: add the DFL EMIF private feature driver
Date: Tue, 27 Oct 2020 11:55:45 +0100	[thread overview]
Message-ID: <20201027105545.GB20676@kozik-lap> (raw)
In-Reply-To: <1603790581-4487-3-git-send-email-yilun.xu@intel.com>

On Tue, Oct 27, 2020 at 05:23:01PM +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>
> Reviewed-by: Tom Rix <trix@redhat.com>
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>

Feel free to take it via DFL tree.

Best regards,
Krzysztof

      reply	other threads:[~2020-10-27 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27  9:22 [PATCH v11 0/2] add DFL bus support to MODULE_DEVICE_TABLE() Xu Yilun
2020-10-27  9:23 ` [PATCH v11 1/2] fpga: dfl: add support for N3000 Nios private feature Xu Yilun
2020-10-27 10:54   ` Krzysztof Kozlowski
2020-10-27  9:23 ` [PATCH v11 2/2] memory: dfl-emif: add the DFL EMIF private feature driver Xu Yilun
2020-10-27 10:55   ` Krzysztof Kozlowski [this message]

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=20201027105545.GB20676@kozik-lap \
    --to=krzk@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).