summaryrefslogtreecommitdiff
path: root/drivers/nfc/s3fwrn5
diff options
context:
space:
mode:
authorSamuel Ortiz <sameo@linux.intel.com>2015-10-03 06:02:28 +0300
committerSamuel Ortiz <sameo@linux.intel.com>2015-10-03 06:18:55 +0300
commit21d19f87d483fbac66ca24863b8c8d52a7ab539d (patch)
treee4b80a23f7a77eb325d01283cdf9cebd485ec760 /drivers/nfc/s3fwrn5
parentf6d3125fa3c2f55ddf7cf69365c41089de6cfae6 (diff)
downloadlinux-21d19f87d483fbac66ca24863b8c8d52a7ab539d.tar.xz
NFC: nci: Use __nci_request for exported routines
Since we do not know in which context drivers will call these routines, they should use the unlocked version of nci_request, i.e. __nci_request. It is up to drivers to know/decide if they need to take the req_lock mutex before calling those routines. When being called from the NCI setup routine there is no need to do so as ops->setup is called under req_lock. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/nfc/s3fwrn5')
0 files changed, 0 insertions, 0 deletions