From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: cgzones@googlemail.com, Jan Kara <jack@suse.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Casey Schaufler <casey@schaufler-ca.com>,
"peterz@infradead.org" <peterz@infradead.org>,
Sohil Mehta <sohil.mehta@intel.com>,
Miklos Szeredi <mszeredi@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH] fs/xattr: unify *at syscalls
Date: Thu, 2 May 2024 15:04:26 +0200 [thread overview]
Message-ID: <20240502-wegweisend-hippen-75aae5b9da3f@brauner> (raw)
In-Reply-To: <20240502103716.avdfm6r3ma2wfxjj@quack3>
On Thu, May 02, 2024 at 12:37:16PM +0200, Jan Kara wrote:
> On Tue 30-04-24 17:19:14, Christian Göttsche wrote:
> > From: Christian Göttsche <cgzones@googlemail.com>
> >
> > Use the same parameter ordering for all four newly added *xattrat
> > syscalls:
> >
> > dirfd, pathname, at_flags, ...
> >
> > Also consistently use unsigned int as the type for at_flags.
> >
> > Suggested-by: Jan Kara <jack@suse.com>
> > Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
>
> Thanks! The change looks good to me. Christian, do you plan to fold this
> into the series you've taken to your tree?
Yep, that's the plan.
next prev parent reply other threads:[~2024-05-02 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:19 [PATCH] fs/xattr: unify *at syscalls Christian Göttsche
2024-05-02 10:37 ` Jan Kara
2024-05-02 13:04 ` Christian Brauner [this message]
2024-05-02 13:02 ` Christian Brauner
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=20240502-wegweisend-hippen-75aae5b9da3f@brauner \
--to=brauner@kernel.org \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=cgzones@googlemail.com \
--cc=geert@linux-m68k.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mszeredi@redhat.com \
--cc=peterz@infradead.org \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).