diff options
author | Mark Brown <broonie@opensource.wolfsonmicro.com> | 2012-02-17 10:46:00 -0800 |
---|---|---|
committer | Grant Likely <grant.likely@secretlab.ca> | 2012-03-05 08:05:08 -0700 |
commit | e4e449e82871c53ef3b22bd3a50fceabc0638926 (patch) | |
tree | 87e14ac729928d7e1c54e7a975b365714c50bf85 /drivers/vhost | |
parent | 25553ff0756c59b617af6bdd280c94e943164184 (diff) | |
download | blackbird-op-linux-e4e449e82871c53ef3b22bd3a50fceabc0638926.tar.gz blackbird-op-linux-e4e449e82871c53ef3b22bd3a50fceabc0638926.zip |
gpiolib: Add comments explaining the _cansleep() WARN_ON()s
I've seen users getting very confused by the WARN_ON()s for can_sleep
GPIOs in the atomic-safe paths, the discoverability of the non-atomic
version of the API seems to be hampered by the fact that it's defined
in a header file not the .c file where the warnings are.
Add a couple of comments next to the warnings to help people on their
way.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Diffstat (limited to 'drivers/vhost')
0 files changed, 0 insertions, 0 deletions