From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCHES] d_path-related stuff
Date: Thu, 18 Aug 2022 04:06:36 +0100 [thread overview]
Message-ID: <Yv2svMjjnMVrHwo0@ZenIV> (raw)
Patches in vfs.git #work.d_path (and just posted
to fsdevel); assorted d_path-related stuff that had fallen
through the cracks last cycle (or several). Posted this
time around, will go into -next if nobody screams...
dynamic_dname(): drop unused dentry argument
ksmbd: don't open-code file_path()
->getprocattr(): attribute name is const char *, TYVM...
ksmbd: don't open-code %pf
d_path.c: typo fix...
reply other threads:[~2022-08-18 3:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yv2svMjjnMVrHwo0@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox