From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Christian Brauner <brauner@kernel.org>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 1/1 fyi] tools include UAPI: Sync linux/fcntl.h copy with the kernel sources
Date: Mon, 30 Sep 2024 17:23:50 -0300 [thread overview]
Message-ID: <ZvsI1lYepcADsyMC@x1> (raw)
In-Reply-To: <20240930.162315-undated.permit.modular.catnip-THGkg7JTJlP@cyphar.com>
On Mon, Sep 30, 2024 at 06:24:50PM +0200, Aleksa Sarai wrote:
> On 2024-09-30, Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Picking the changes from:
> >
> > 4356d575ef0f39a3 ("fhandle: expose u64 mount id to name_to_handle_at(2)")
> > b4fef22c2fb97fa2 ("uapi: explain how per-syscall AT_* flags should be allocated")
> > 820a185896b77814 ("fcntl: add F_CREATED_QUERY")
> >
> > It just moves AT_REMOVEDIR around, and adds a bunch more AT_ for
> > renameat2() and name_to_handle_at(). We need to improve this situation,
> > as not all AT_ defines are applicable to all fs flags...
> >
> > This adds support for those new AT_ defines, addressing this build
> > warning:
> >
> > diff -u tools/perf/trace/beauty/include/uapi/sound/asound.h include/uapi/sound/asound.h
>
> Thanks, feel free to take my
>
> Reviewed-by: Aleksa Sarai <cyphar@cyphar.com>
Thanks, added.
- Arnaldo
prev parent reply other threads:[~2024-09-30 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 15:47 [PATCH 1/1 fyi] tools include UAPI: Sync linux/fcntl.h copy with the kernel sources Arnaldo Carvalho de Melo
2024-09-30 16:24 ` Aleksa Sarai
2024-09-30 20:23 ` Arnaldo Carvalho de Melo [this message]
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=ZvsI1lYepcADsyMC@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=tj@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