From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] xattr stuff
Date: Fri, 15 Nov 2024 15:33:44 +0000 [thread overview]
Message-ID: <20241115153344.GW3387508@ZenIV> (raw)
In-Reply-To: <20241115150806.GU3387508@ZenIV>
On Fri, Nov 15, 2024 at 03:08:06PM +0000, Al Viro wrote:
[snip]
> Al Viro (9):
> teach filename_lookup() to treat NULL filename as ""
> getname_maybe_null() - the third variant of pathname copy-in
PS: there's one more pile in -next (statx stuff), but it shares the
first two commits with this branch, so I'll probably send a pull request
once this one gets merged, if that's OK by you.
next prev parent reply other threads:[~2024-11-15 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 15:08 [git pull] xattr stuff Al Viro
2024-11-15 15:33 ` Al Viro [this message]
2024-11-18 21:38 ` [git pull] statx stuff Al Viro
2024-11-18 22:57 ` pr-tracker-bot
2024-11-18 21:00 ` [git pull] xattr stuff pr-tracker-bot
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=20241115153344.GW3387508@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.