On 6/7/2016 4:21 PM, Auger Eric wrote:
>> -vfio_platform_call_reset(vdev, NULL);
>> > + ret = vfio_platform_call_reset(vdev, _dbg);
>> > + if (ret && vdev->reset_required) {
>> > + dev_warn(vdev->device, "reset driver is required and
>> > reset call
On 6/7/2016 4:21 PM, Auger Eric wrote:
>> -vfio_platform_call_reset(vdev, NULL);
>> > + ret = vfio_platform_call_reset(vdev, _dbg);
>> > + if (ret && vdev->reset_required) {
>> > + dev_warn(vdev->device, "reset driver is required and
>> > reset call
Hi Sinan,
Le 29/05/2016 à 00:01, Sinan Kaya a écrit :
> Open call is ignoring the return code from reset call and can
> potentially continue even though reset call failed.
>
> If reset_required module parameter is set, this patch is going
> to validate the return code and will abort open if reset
Hi Sinan,
Le 29/05/2016 à 00:01, Sinan Kaya a écrit :
> Open call is ignoring the return code from reset call and can
> potentially continue even though reset call failed.
>
> If reset_required module parameter is set, this patch is going
> to validate the return code and will abort open if reset
Open call is ignoring the return code from reset call and can
potentially continue even though reset call failed.
If reset_required module parameter is set, this patch is going
to validate the return code and will abort open if reset fails.
Signed-off-by: Sinan Kaya
---
Open call is ignoring the return code from reset call and can
potentially continue even though reset call failed.
If reset_required module parameter is set, this patch is going
to validate the return code and will abort open if reset fails.
Signed-off-by: Sinan Kaya
---
6 matches
Mail list logo