diff options
| author | Jeff Layton <jeff.layton@primarydata.com> | 2015-04-03 09:04:04 -0400 |
|---|---|---|
| committer | Jeff Layton <jeff.layton@primarydata.com> | 2015-04-03 09:04:04 -0400 |
| commit | 3648888e90bb7fe6d0586ec177511e6678ee22c3 (patch) | |
| tree | 8f23ef5421f8ace7d3a1e8bcc07be92ac03b4c25 /crypto/crypto_null.c | |
| parent | cae80b305e1c3944746dd93e33e9b2ccd5a490c1 (diff) | |
| download | op-kernel-dev-3648888e90bb7fe6d0586ec177511e6678ee22c3.zip op-kernel-dev-3648888e90bb7fe6d0586ec177511e6678ee22c3.tar.gz | |
locks: get rid of WE_CAN_BREAK_LSLK_NOW dead code
As Bruce points out, there's no compelling reason to change /proc/locks
output at this point. If we did want to do this, then we'd almost
certainly want to introduce a new file to display this info (maybe via
debugfs?).
Let's remove the dead WE_CAN_BREAK_LSLK_NOW ifdef here and just plan to
stay with the legacy format.
Reported-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Diffstat (limited to 'crypto/crypto_null.c')
0 files changed, 0 insertions, 0 deletions
