From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Will Deacon <will@kernel.org>
Cc: mtk.manpages@gmail.com, Dave Martin <Dave.Martin@arm.com>,
linux-arch@vger.kernel.org, linux-man@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: RFC: Adding arch-specific user ABI documentation in linux-man
Date: Wed, 6 May 2020 12:47:33 +0200 [thread overview]
Message-ID: <a86c4f3e-b50e-0541-074f-1bfcb4a93b5d@gmail.com> (raw)
In-Reply-To: <20200505124351.GF1551@shell.armlinux.org.uk>
On 5/5/20 2:43 PM, Russell King - ARM Linux admin wrote:
> On Tue, May 05, 2020 at 11:44:55AM +0100, Will Deacon wrote:
>> Michael has been nagging me on and off about that for, what, 10 years now?
>> I would therefore be very much in favour of having our ptrace extensions
>> documented!
>>
>> We could even put this stuff under Documentation/arm64/man/ if it's deemed
>> too CPU-specific for the man-pages project, but my preference would still
>> be for it to be hosted there alongside all the other man pages.
>
> Stuffing random things into the kernel tree is painful for some people.
Yes, and too often not easily noticeable for user-space programmers.
>
> For example, if you cross-build your kernel, then the stuff in the
> tools/ subdirectory is totally useless (I think everything except
> perf) because you can't build it.
>
> Let's stop making the mistake of constantly shoving stuff into the
> kernel source tree.
Agrred.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-05-06 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:32 RFC: Adding arch-specific user ABI documentation in linux-man Dave Martin
2020-05-05 7:45 ` AW: " Walter Harms
2020-05-05 10:55 ` Dave Martin
2020-05-05 10:44 ` RFC: " Will Deacon
2020-05-05 11:05 ` Dave Martin
2020-05-05 12:14 ` Will Deacon
2020-05-06 10:47 ` Michael Kerrisk (man-pages)
2020-05-05 12:43 ` Russell King - ARM Linux admin
2020-05-05 13:06 ` Will Deacon
2020-05-05 13:16 ` Russell King - ARM Linux admin
2020-05-06 10:47 ` Michael Kerrisk (man-pages) [this message]
2020-05-06 10:47 ` Michael Kerrisk (man-pages)
2020-05-06 10:47 ` Michael Kerrisk (man-pages)
2020-05-06 14:29 ` Dave Martin
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=a86c4f3e-b50e-0541-074f-1bfcb4a93b5d@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-man@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=vincenzo.frascino@arm.com \
--cc=will@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).