From: Alan Tull <delicious.quinoa@gmail.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Moritz Fischer" <mdf@kernel.org>,
linux-fpga@vger.kernel.org,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] fpga: Add flag to indicate bitstream needs decrypting
Date: Tue, 21 Feb 2017 12:38:14 -0600 [thread overview]
Message-ID: <CANk1AXRwCKA9VPwzVyOOD5sGEnE97+dpQVdjDKvzt_Jq0Epm5Q@mail.gmail.com> (raw)
In-Reply-To: <a006fb8e-b7a3-926b-5158-a53d190c31e1@xilinx.com>
On Tue, Feb 21, 2017 at 12:36 PM, Michal Simek <michal.simek@xilinx.com> wrote:
> On 21.2.2017 19:26, Alan Tull wrote:
>> 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?
>
> Can I know the reason for this? I know that there were some discussion
> in past. But just add them to your linux-fpga.git repo and send pull
> request to Greg and proper time when he expects that.
>
Greg said it was easier for him to take them from email.
Alan
> Thanks,
> Michal
>
next prev parent reply other threads:[~2017-02-21 18:38 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
2017-02-21 18:36 ` Michal Simek
2017-02-21 18:38 ` Alan Tull [this message]
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=CANk1AXRwCKA9VPwzVyOOD5sGEnE97+dpQVdjDKvzt_Jq0Epm5Q@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).