From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>,
Thorsten Leemhuis <linux@leemhuis.info>
Cc: linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/1] RFC: Revamp admin-guide/tainted-kernels.rst to make it more comprehensible
Date: Thu, 20 Dec 2018 08:38:06 -0800 [thread overview]
Message-ID: <a02caf89-9221-8e31-4a2d-44b46b81cda2@infradead.org> (raw)
In-Reply-To: <20181220082819.69fc3e5c@lwn.net>
On 12/20/18 7:28 AM, Jonathan Corbet wrote:
> On Thu, 20 Dec 2018 16:23:38 +0100
> Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
>> While at it: Jonathan, you mentioned putting the script in scripts/, but
>> according to the Makefile in that directory it is "for various helper
>> programs used throughout the kernel for the build process". That's one
>> reason why it feels wrong to put it there. Another one: that script
>> targets users and thus we should try to make sure they can access it
>> easily. That's why I'm currently inclined to put it in tools/ somewhere.
>
> Yeah, tools/ is a better place. Maybe a tools/debugging directory or some
> such?
chktaint is similar (IMO) to scripts/decodecode though.
@Thorsten:
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
thanks,
--
~Randy
next prev parent reply other threads:[~2018-12-20 16:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 15:20 [PATCH 0/1] RFC: Revamp admin-guide/tainted-kernels.rst to make it more comprehensible Thorsten Leemhuis
2018-12-17 15:20 ` [PATCH 1/1] docs: Revamp tainted-kernels.rst " Thorsten Leemhuis
2018-12-17 21:14 ` Randy Dunlap
2018-12-17 18:24 ` [PATCH 0/1] RFC: Revamp admin-guide/tainted-kernels.rst " Jonathan Corbet
2018-12-17 21:06 ` Randy Dunlap
2018-12-20 15:23 ` Thorsten Leemhuis
2018-12-20 15:28 ` Jonathan Corbet
2018-12-20 16:38 ` Randy Dunlap [this message]
2018-12-20 18:21 ` Thorsten Leemhuis
2018-12-20 20:10 ` Randy Dunlap
2018-12-21 12:31 ` Thorsten Leemhuis
2018-12-20 16:42 ` Randy Dunlap
2018-12-21 15:26 ` Thorsten Leemhuis
2019-01-03 9:32 ` Thorsten Leemhuis
2019-01-03 18:12 ` Jonathan Corbet
2019-01-07 18:56 ` Thorsten Leemhuis
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=a02caf89-9221-8e31-4a2d-44b46b81cda2@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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).