get rid of fs_value_is_filename_empty
Its behaviour is identical to that of fs_value_is_filename. It makes no sense, anyway - LOOKUP_EMPTY affects nothing whatsoever once the pathname has been imported from userland. And both fs_value_is_filename and fs_value_is_filename_empty carry an already imported pathname. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
@@ -427,7 +427,6 @@ returned.
|
||||
fs_value_is_string, Value is a string
|
||||
fs_value_is_blob, Value is a binary blob
|
||||
fs_value_is_filename, Value is a filename* + dirfd
|
||||
fs_value_is_filename_empty, Value is a filename* + dirfd + AT_EMPTY_PATH
|
||||
fs_value_is_file, Value is an open file (file*)
|
||||
|
||||
If there is a value, that value is stored in a union in the struct in one
|
||||
|
Reference in New Issue
Block a user