Hi Hannes,
Thanks,
>From facts.MaxDevHandle value from firmware, driver will get to know
the max device handle or devices that it can support. Based on that
value only driver will allocate memory for bit mapping.
And driver will not receive any events from controller, if it exceeds
the max
Hi Hannes,
Thanks,
>From facts.MaxDevHandle value from firmware, driver will get to know
the max device handle or devices that it can support. Based on that
value only driver will allocate memory for bit mapping.
And driver will not receive any events from controller, if it exceeds
the max
On 10/25/2016 11:19 AM, Suganath Prabu Subramani wrote:
> Hi Hannes,
>
> Please give us little more info on the third comment. It ll help us to
> understand better and
> incorporate required changes.
>
> Comment is "Why don't you need to check for the size of the bitmap here?"
>
> i have taken
On 10/25/2016 11:19 AM, Suganath Prabu Subramani wrote:
> Hi Hannes,
>
> Please give us little more info on the third comment. It ll help us to
> understand better and
> incorporate required changes.
>
> Comment is "Why don't you need to check for the size of the bitmap here?"
>
> i have taken
Hi Hannes,
Please give us little more info on the third comment. It ll help us to
understand better and
incorporate required changes.
Comment is "Why don't you need to check for the size of the bitmap here?"
i have taken care of other two comments in this patch.
> /* check if device is
Hi Hannes,
Please give us little more info on the third comment. It ll help us to
understand better and
incorporate required changes.
Comment is "Why don't you need to check for the size of the bitmap here?"
i have taken care of other two comments in this patch.
> /* check if device is
On 10/20/2016 02:20 PM, Suganath Prabu S wrote:
When device missing event arrives, device_remove_in_progress bit will be
set and hence driver has to stop sending IOCTL commands.Now the check has
been added in IOCTL path to test device_remove_in_progress bit is set, if
so then IOCTL will be
On 10/20/2016 02:20 PM, Suganath Prabu S wrote:
When device missing event arrives, device_remove_in_progress bit will be
set and hence driver has to stop sending IOCTL commands.Now the check has
been added in IOCTL path to test device_remove_in_progress bit is set, if
so then IOCTL will be
When device missing event arrives, device_remove_in_progress bit will be
set and hence driver has to stop sending IOCTL commands.Now the check has
been added in IOCTL path to test device_remove_in_progress bit is set, if
so then IOCTL will be failed printing failure message.
Signed-off-by:
When device missing event arrives, device_remove_in_progress bit will be
set and hence driver has to stop sending IOCTL commands.Now the check has
been added in IOCTL path to test device_remove_in_progress bit is set, if
so then IOCTL will be failed printing failure message.
Signed-off-by:
10 matches
Mail list logo