linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: Xu Yilun <yilun.xu@intel.com>,
	mdf@kernel.org, hao.wu@intel.com, trix@redhat.com,
	linux-fpga@vger.kernel.org, Richard Gong <richard.gong@intel.com>
Subject: Re: [PATCH] firmware: stratix10-svc: extend SVC driver to get the firmware version
Date: Tue, 25 Jan 2022 20:54:48 -0800	[thread overview]
Message-ID: <YfDUGD5+hqOnSNjP@epycbox.lan> (raw)
In-Reply-To: <5a1b6658-062c-d777-69d3-6a053d087ca6@kernel.org>

Dinh,

On Tue, Jan 25, 2022 at 10:31:06PM -0600, Dinh Nguyen wrote:
> 
> 
> On 1/25/22 19:07, Xu Yilun wrote:
> > On Tue, Jan 25, 2022 at 01:28:53PM -0600, Dinh Nguyen wrote:
> > > From: Richard Gong <richard.gong@intel.com>
> > > 
> > > Extend Intel service layer driver to get the firmware version running at
> > > FPGA device. Therefore FPGA manager driver, one of Intel service layer
> > > driver's client, can decide whether to handle the newly added bitstream
> > > authentication function based on the retrieved firmware version.
> > > 
> > > Acked-by: Moritz Fischr <mdf@kernel.org>
> > 
> > This is already acked and no more change, is it? So please just ping in
> > the original mail or add the [RESEND PATCH] prefix.
> > 
> > The patch is good to me.
> > 
> > Acked-by: Xu Yilun <yilun.xu@intel.com>
> > 
> 
> Thanks, I added Moritz Acked-by: is the only change.
> 
> Dinh

Did we traditionally take those through FPGA tree, did Greg pick those
up?

Cheers,
Moritz

  reply	other threads:[~2022-01-26  4:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 19:28 [PATCH] firmware: stratix10-svc: extend SVC driver to get the firmware version Dinh Nguyen
2022-01-26  1:07 ` Xu Yilun
2022-01-26  4:31   ` Dinh Nguyen
2022-01-26  4:54     ` Moritz Fischer [this message]
2022-01-26 15:56       ` Dinh Nguyen
2022-01-27  0:39       ` Xu Yilun
2022-01-27  2:56         ` Dinh Nguyen
2022-02-16 16:15       ` Dinh Nguyen

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=YfDUGD5+hqOnSNjP@epycbox.lan \
    --to=mdf@kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=richard.gong@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).