On Wednesday, July 25, 2018 6:33:44 PM CEST Alan Tull wrote:
> On Wed, Jul 11, 2018 at 10:59 AM, Alan Tull wrote:
> > On Wed, Jul 11, 2018 at 7:38 AM, Federico Vaga
> > wrote:
> >
> > Hi Federico,
> >
> >> Hi Alan,
> >>
> >> I have another point that I would like to discuss. It is about the
>
On Wed, Jul 11, 2018 at 10:59 AM, Alan Tull wrote:
> On Wed, Jul 11, 2018 at 7:38 AM, Federico Vaga wrote:
>
> Hi Federico,
>
>> Hi Alan,
>>
>> I have another point that I would like to discuss. It is about the
>> usage of 'fpga_mgr_free()' which does not look like consistent.
>>
>> This function
Hi Alan,
On Wed, Jul 11, 2018 at 10:59:01AM -0500, Alan Tull wrote:
> On Wed, Jul 11, 2018 at 7:38 AM, Federico Vaga wrote:
[..]
> > This makes the usage consistent: the user creates and destroy its own
> > objects. This is also consistent with our other discussion where we
> > said, among the o
On Wed, Jul 11, 2018 at 7:38 AM, Federico Vaga wrote:
Hi Federico,
> Hi Alan,
>
> I have another point that I would like to discuss. It is about the
> usage of 'fpga_mgr_free()' which does not look like consistent.
>
> This function, according to the current implementation, can be used by
> an F
Hi Alan,
I have another point that I would like to discuss. It is about the
usage of 'fpga_mgr_free()' which does not look like consistent.
This function, according to the current implementation, can be used by
an FPGA manager user and it is used by the FPGA manager itself on
device release. T
5 matches
Mail list logo