linux-kernel - Re: [GIT PULL] fpga: Updates for 4.10-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 4 Jan 2017 15:53:18 -0600
From:   Alan Tull <atull@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Moritz Fischer <moritz.fischer@...us.com>,
        linux-fpga@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        atull <atull@...nsource.altera.com>, dinguyen@...nel.org
Subject: Re: [GIT PULL] fpga: Updates for 4.10-rc2

On Wed, Jan 4, 2017 at 3:28 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Wed, Jan 04, 2017 at 02:00:23PM -0600, Alan Tull wrote:
>> Hi Greg,
>>
>> Please pull these changes for FPGA.
>>
>> Thanks!
>> Alan
>>
>> The following changes since commit e3d31bda06e43968cd215ae590eb7cda827f01e9:
>>
>>   Add linux-next specific files for 20161224 (2017-01-04 10:26:49 -0600)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/atull/linux-fpga.git tags/fpga-for-greg-20170104
>>
>> for you to fetch changes up to 2dd088da8cce745c008fc7f8b64e1aef33eb37c2:
>>
>>   ARM: ep93xx: Register ts73xx-fpga manager driver for TS-7300 (2017-01-04 10:27:26 -0600)
>>
>> ----------------------------------------------------------------
>> fpga: Updates for 4.10-rc2
>>
>>  * Add scatterlist based fpga programming
>>  * TS-7300 FPGA manager
>>  * zynq: Check for errors after completing DMA
>>  * fix sparse warnings in fpga-mgr and fpga-bridge
>
> These are all bugfixes or regression fixes?  Doesn't seem like adding
> new functionality and a new driver fits that category to me, why add
> them now?
>
> Sorry, I can't take this, if you resend them as patches, I can be more
> specific...
>
> thanks,
>
> greg k-h

Hi Greg,

Yes, sorry, I'm still learning here.  One patch is a fix (sparse
errors), the rest are new functionality.

Would it be appropriate to separate these and send you two pull
requests -  the sparse error fix for 4.10 and the rest (new
functionality) for 4.11?

Alan