From: Richard Gong <richard.gong@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: mdf@kernel.org, trix@redhat.com, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org, dinguyen@kernel.org,
sridhar.rajagopal@intel.com, richard.gong@intel.com
Subject: Re: [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region
Date: Mon, 14 Dec 2020 08:43:12 -0600 [thread overview]
Message-ID: <f5227d19-895a-e43f-a5eb-4fb86ddcc52f@linux.intel.com> (raw)
In-Reply-To: <X9dxE/jQ33mfWBz/@kroah.com>
Hi Greg,
On 12/14/20 8:05 AM, Greg KH wrote:
> On Mon, Dec 14, 2020 at 08:03:07AM -0600, Richard Gong wrote:
>>
>> Hi Moritz, Greg,
>>
>> Sorry for asking.
>>
>> Any comment on Intel service layer and FPGA patches submitted on 11/18/20?
>
> I don't see them in my review queue, sorry.
>
I just re-submitted the patches.
> greg k-h >
Regards,
Richard
prev parent reply other threads:[~2020-12-14 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:29 [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region richard.gong
2020-11-18 14:29 ` [PATCHv2 1/5] firmware: stratix10-svc: add COMMAND_AUTHENTICATE_BITSTREAM flag richard.gong
2020-11-18 15:30 ` Moritz Fischer
2020-11-18 18:16 ` Richard Gong
2020-11-22 1:10 ` Moritz Fischer
2020-11-30 18:55 ` Richard Gong
2020-12-01 4:31 ` Moritz Fischer
2020-12-01 19:30 ` Richard Gong
2020-12-01 19:19 ` Moritz Fischer
2020-12-01 20:52 ` Richard Gong
2020-11-18 14:29 ` [PATCHv2 2/5] fpga: fpga-mgr: add FPGA_MGR_BITSTREM_AUTHENTICATION flag richard.gong
2020-11-18 14:29 ` [PATCHv2 3/5] fpga: of-fpga-region: add authenticate-fpga-config property richard.gong
2020-11-18 14:29 ` [PATCHv2 4/5] dt-bindings: fpga: " richard.gong
2020-11-18 14:29 ` [PATCHv2 5/5] fpga: stratix10-soc: extend driver for bitstream authentication richard.gong
2020-12-14 14:03 ` [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region Richard Gong
2020-12-14 14:05 ` Greg KH
2020-12-14 14:43 ` Richard Gong [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=f5227d19-895a-e43f-a5eb-4fb86ddcc52f@linux.intel.com \
--to=richard.gong@linux.intel.com \
--cc=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=richard.gong@intel.com \
--cc=sridhar.rajagopal@intel.com \
--cc=trix@redhat.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).