summaryrefslogtreecommitdiff
path: root/include/uapi
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2023-11-10 15:24:45 -0500
committerAl Viro <viro@zeniv.linux.org.uk>2023-11-18 16:21:38 -0500
commit2fcd38f4de7256e2b5cb23ad22a6e3ebfea7dd18 (patch)
treeb55b85221eec432a8e116181fc1b5839f8c6f362 /include/uapi
parent0d486510f86eb8162022ed61e6dc424a10909a10 (diff)
[software coproarchaeology] dentry.h: kill a mysterious comment
there's a strange comment in front of d_lookup() declaration: /* appendix may either be NULL or be used for transname suffixes */ Looks like nobody had been curious enough to track its history; it predates git, it predates bitkeeper and if you look through the pre-BK trees, you finally arrive at this in 2.1.44-for-davem: /* appendix may either be NULL or be used for transname suffixes */ -extern struct dentry * d_lookup(struct inode * dir, struct qstr * name, - struct qstr * appendix); +extern struct dentry * d_lookup(struct dentry * dir, struct qstr * name); In other words, it refers to the third argument d_lookup() used to have back then. It had been introduced in 2.1.43-pre, on June 12 1997, along with d_lookup(), only to be removed by July 4 1997, presumably when the Cthulhu-awful thing it used to be used for (look for CONFIG_TRANS_NAMES in 2.1.43-pre, and keep a heavy-duty barfbag ready) had been, er, noticed and recognized for what it had been. Despite the appendectomy, the comment remained. Some things really need to be put out of their misery... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'include/uapi')
0 files changed, 0 insertions, 0 deletions