From: Alan Tull <delicious.quinoa@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Moritz Fischer" <mdf@kernel.org>,
linux-fpga@vger.kernel.org,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Michal Simek" <michal.simek@xilinx.com>
Subject: Re: [PATCH v2 1/3] fpga: Add flag to indicate bitstream needs decrypting
Date: Tue, 21 Feb 2017 12:26:17 -0600 [thread overview]
Message-ID: <CANk1AXR3RK3na3h+EgPAcfjS2+4QRSqCZVKcJWHS=adcrpe=4w@mail.gmail.com> (raw)
In-Reply-To: <CANk1AXQ6Tf3MtHV2_iJ8cHxG71HYehQbZfcuKgK9124zCpS-nA@mail.gmail.com>
On Tue, Feb 21, 2017 at 10:35 AM, Alan Tull <delicious.quinoa@gmail.com>
Hi Greg,
Would it be helpful for us to resend patches for you to take with you
on cc? Or is it enough that they are on lkml?
Thanks,
Alan Tull
wrote:
> On Tue, Feb 21, 2017 at 7:55 AM, Michal Simek <michal.simek@xilinx.com> wrote:
>> On 20.2.2017 21:55, mdf@kernel.org wrote:
>>> From: Moritz Fischer <mdf@kernel.org>
>>>
>>> Add a flag that is passed to the write_init() callback, indicating
>>> that the bitstream is encrypted.
>>>
>>> The low-level driver will deal with the flag, or return an error,
>>> if encrypted bitstreams are not supported.
>>>
>>> Signed-off-by: Moritz Fischer <mdf@kernel.org>
>>> Cc: Alan Tull <atull@kernel.org>
>>> Cc: Michal Simek <michal.simek@xilinx.com>
>>> Cc: Sören Brinkmann <soren.brinkmann@xilinx.com>
>>> Cc: linux-kernel@vger.kernel.org
>>> Cc: linux-fpga@vger.kernel.org
>>> ---
>>>
>>> Changes from v1:
>>> - Renamed flag from FPGA_MGR_DECRYPT_BITSTREAM->FPGA_MGR_ENCRYPTED_BITSTREAM
>>>
>>> ---
>>> include/linux/fpga/fpga-mgr.h | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/include/linux/fpga/fpga-mgr.h b/include/linux/fpga/fpga-mgr.h
>>> index 57beb5d..e2ef94f 100644
>>> --- a/include/linux/fpga/fpga-mgr.h
>>> +++ b/include/linux/fpga/fpga-mgr.h
>>> @@ -70,6 +70,7 @@ enum fpga_mgr_states {
>>> */
>>> #define FPGA_MGR_PARTIAL_RECONFIG BIT(0)
>>> #define FPGA_MGR_EXTERNAL_CONFIG BIT(1)
>>> +#define FPGA_MGR_ENCRYPTED_BITSTREAM BIT(2)
>>>
>>> /**
>>> * struct fpga_image_info - information specific to a FPGA image
>>>
>>
>> Acked-by: Michal Simek <michal.simek@xilinx.com>
>
> Acked-by: Alan Tull <atull@kernel.org>
>
>>
>> Thanks,
>> Michal
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-fpga" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-21 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 20:55 [PATCH v2 1/3] fpga: Add flag to indicate bitstream needs decrypting mdf
2017-02-20 20:55 ` [PATCH v2 2/3] fpga: zynq: Add support for encrypted bitstreams mdf
2017-02-21 13:55 ` Michal Simek
2017-02-21 16:36 ` Alan Tull
2017-02-20 20:55 ` [PATCH v2 3/3] fpga: region: Add fpga-region property 'encrypted-fpga-config' mdf
2017-02-21 13:55 ` Michal Simek
2017-02-21 16:36 ` Alan Tull
2017-02-21 13:55 ` [PATCH v2 1/3] fpga: Add flag to indicate bitstream needs decrypting Michal Simek
2017-02-21 16:35 ` Alan Tull
2017-02-21 18:26 ` Alan Tull [this message]
2017-02-21 18:36 ` Michal Simek
2017-02-21 18:38 ` Alan Tull
2017-02-22 7:15 ` Greg Kroah-Hartman
2017-02-22 8:22 ` Michal Simek
2017-02-22 13:04 ` Greg Kroah-Hartman
2017-02-22 13:24 ` Michal Simek
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='CANk1AXR3RK3na3h+EgPAcfjS2+4QRSqCZVKcJWHS=adcrpe=4w@mail.gmail.com' \
--to=delicious.quinoa@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=soren.brinkmann@xilinx.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).