From: Peter Zijlstra <peterz@infradead•org>
To: "André Almeida" <andrealmeid@collabora•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Ingo Molnar <mingo@redhat•com>, "H . Peter Anvin" <hpa@zytor•com>,
Jonathan Corbet <corbet@lwn•net>
Subject: Re: [PATCH] docs: futex: Fix kernel-doc references
Date: Tue, 19 Oct 2021 15:20:45 +0200 [thread overview]
Message-ID: <YW7GLTdP3TAcg9Ac@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20211012135549.14451-1-andrealmeid@collabora.com>
On Tue, Oct 12, 2021 at 10:55:49AM -0300, André Almeida wrote:
> Since the futex code was restructured, there's no futex.c file anymore
> and the implementation is split in various files. Point kernel-doc
> references to the new files.
>
> Signed-off-by: André Almeida <andrealmeid@collabora•com>
Thanks!
prev parent reply other threads:[~2021-10-19 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 13:55 [PATCH] docs: futex: Fix kernel-doc references André Almeida
2021-10-19 13:20 ` Peter Zijlstra [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=YW7GLTdP3TAcg9Ac@hirez.programming.kicks-ass.net \
--to=peterz@infradead$(echo .)org \
--cc=andrealmeid@collabora$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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