On Thu, Aug 17, 2017 at 2:42 PM, Moritz Fischer
wrote:
> Hi Alan,
>
> I think that should go together with [3/16] in one commit,
> to make API change go together with actual change?
Yes, the patches will be going in together anyway (not through
separate maintainers), so
On Thu, Aug 17, 2017 at 2:42 PM, Moritz Fischer
wrote:
> Hi Alan,
>
> I think that should go together with [3/16] in one commit,
> to make API change go together with actual change?
Yes, the patches will be going in together anyway (not through
separate maintainers), so I could do that. I hope
Hi Alan,
I think that should go together with [3/16] in one commit,
to make API change go together with actual change?
On Thu, Jul 6, 2017 at 11:47 AM, Alan Tull wrote:
> The FPGA manager has been simplified to have a single
> fpga_mgr_load function which replaces the three
>
Hi Alan,
I think that should go together with [3/16] in one commit,
to make API change go together with actual change?
On Thu, Jul 6, 2017 at 11:47 AM, Alan Tull wrote:
> The FPGA manager has been simplified to have a single
> fpga_mgr_load function which replaces the three
> fpga_mgr_*load*
The FPGA manager has been simplified to have a single
fpga_mgr_load function which replaces the three
fpga_mgr_*load* functions.
The parameters presenting the FPGA image have been
added to struct fpga_image_info.
Additional functions have been added to alloc/free
fpga_image_info.
Getting a FPGA
The FPGA manager has been simplified to have a single
fpga_mgr_load function which replaces the three
fpga_mgr_*load* functions.
The parameters presenting the FPGA image have been
added to struct fpga_image_info.
Additional functions have been added to alloc/free
fpga_image_info.
Getting a FPGA
6 matches
Mail list logo