On 2017-08-29 19:12, David Miller wrote:
Sigh, I had to revert.
You only allow RMNET to take on the values 'y' and 'n'.
You must allow for it to be 'm' and modular as well.
Hi David
I'll fix this now.
Sorry about the cover letter. I'll explain it better in subsequent
submission.
--
Qualco
Sigh, I had to revert.
You only allow RMNET to take on the values 'y' and 'n'.
You must allow for it to be 'm' and modular as well.
From: Subash Abhinov Kasiviswanathan
Date: Tue, 29 Aug 2017 18:47:55 -0600
> I have updated the locking scheme as follows -
Series applied, but this is not how you write a header posting for a
patch set.
This posting is where you say at a high level what the patch series is
doing, how it is doi
Hi David
I have updated the locking scheme as follows -
The shared resource which needs to be protected is realdev->rx_handler_data.
For the writer path, this is using rtnl_lock(). The writer paths are
rmnet_newlink(), rmnet_dellink() and rmnet_force_unassociate_device(). These
paths are already
