From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] prctl.2: tfix
Date: Sat, 1 Apr 2023 00:58:31 +0200 [thread overview]
Message-ID: <4564e7fd-98e6-229e-7b6c-715f2db4ca1a@gmail.com> (raw)
In-Reply-To: <b70fa11b-620e-dea4-3b30-068e0e2740cc@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 961 bytes --]
On 10/11/22 22:53, Alejandro Colomar wrote:
> Hi Jakub,
>
> On 10/11/22 08:25, Jakub Wilk wrote:
>> Escape hyphens.
>>
>> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
>
> Patch applied.
>
> Cheers,
>
> Alex
>
>> ---
>> man2/prctl.2 | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/man2/prctl.2 b/man2/prctl.2
>> index ea6b23229..b91d12af9 100644
>> --- a/man2/prctl.2
>> +++ b/man2/prctl.2
>> @@ -1618,7 +1618,7 @@ or
>> .IP
>> For more information,
>> see the kernel source file
>> -.I Documentation/admin-guide/syscall-user-dispatch.rst
>> +.I Documentation/admin-guide/syscall\-user\-dispatch.rst
I just realized that we missed the first one in that same line :)
>> .\" prctl PR_SET_TAGGED_ADDR_CTRL
>> .\" commit 63f0c60379650d82250f22e4cf4137ef3dc4f43d
>> .TP
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-31 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 6:25 [PATCH] prctl.2: tfix Jakub Wilk
2022-10-11 20:53 ` Alejandro Colomar
2023-03-31 22:58 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 4:05 Eric Biggers
2023-07-15 16:40 ` Alejandro Colomar
2020-07-20 5:49 Jakub Wilk
2020-07-20 9:27 ` Michael Kerrisk (man-pages)
2020-05-25 13:21 Jakub Wilk
2020-05-25 13:24 ` Michael Kerrisk (man-pages)
2020-04-22 9:59 Jakub Wilk
2020-04-22 11:22 ` Michael Kerrisk (man-pages)
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=4564e7fd-98e6-229e-7b6c-715f2db4ca1a@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@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;
as well as URLs for NNTP newsgroup(s).