From: Alan Tull <atull@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
Alan Tull <atull@kernel.org>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: [PATCH 0/4] fpga: zynq: encrypted bitstreams plus one
Date: Mon, 27 Feb 2017 09:18:58 -0600 [thread overview]
Message-ID: <20170227151902.3403-1-atull@kernel.org> (raw)
Hi Greg,
Please take these patches that have been reviewed on the
lkml and linux-fpga lists. Dihn's patch fixes minor sparse
warnings. Moritz's patch adds some functionality for Zynq.
Thanks,
Alan
Dinh Nguyen (1):
fpga: fix sparse warnings in fpga-mgr and fpga-bridge
Moritz Fischer (3):
fpga: Add flag to indicate bitstream needs decrypting
fpga: zynq: Add support for encrypted bitstreams
fpga: region: Add fpga-region property 'encrypted-fpga-config'
.../devicetree/bindings/fpga/fpga-region.txt | 1 +
drivers/fpga/fpga-bridge.c | 2 +-
drivers/fpga/fpga-mgr.c | 2 +-
drivers/fpga/fpga-region.c | 8 +++++--
drivers/fpga/zynq-fpga.c | 28 +++++++++++++++++++---
include/linux/fpga/fpga-mgr.h | 1 +
6 files changed, 35 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-27 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 15:18 Alan Tull [this message]
2017-02-27 15:18 ` [PATCH 1/4] fpga: fix sparse warnings in fpga-mgr and fpga-bridge Alan Tull
2017-02-27 15:19 ` [PATCH 2/4] fpga: Add flag to indicate bitstream needs decrypting Alan Tull
2017-02-27 15:19 ` [PATCH 3/4] fpga: zynq: Add support for encrypted bitstreams Alan Tull
2017-02-27 15:19 ` [PATCH 4/4] fpga: region: Add fpga-region property 'encrypted-fpga-config' Alan Tull
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=20170227151902.3403-1-atull@kernel.org \
--to=atull@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.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).