linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Michal Simek <michal.simek@xilinx.com>
Cc: "Alan Tull" <delicious.quinoa@gmail.com>,
	"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: Wed, 22 Feb 2017 14:24:12 +0100	[thread overview]
Message-ID: <26cac394-2b4b-fbb4-dee6-a9ec3bd2655b@xilinx.com> (raw)
In-Reply-To: <20170222130408.GC15769@kroah.com>

On 22.2.2017 14:04, Greg Kroah-Hartman wrote:
> On Wed, Feb 22, 2017 at 09:22:19AM +0100, Michal Simek wrote:
>> On 22.2.2017 08:15, Greg Kroah-Hartman wrote:
>>> On Tue, Feb 21, 2017 at 12:26:17PM -0600, 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?
>>>
>>> Yes, please send patches with your signed-off-by: for what I should
>>> take.
>>
>> Does it make sense to have git repo in MAINTAINERS file then?
>>
>> T:	git git://git.kernel.org/pub/scm/linux/kernel/git/atull/linux-fpga.git
> 
> Why not, that doesn't mean that's where they get pulled from, but
> rather, where the latest version of the patches can be found at.

ok.

Thanks,
Michal

      reply	other threads:[~2017-02-22 13:24 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
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 [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=26cac394-2b4b-fbb4-dee6-a9ec3bd2655b@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=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=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).