From: Jonathan Corbet <corbet@lwn.net>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Douglas Anderson <dianders@chromium.org>,
Robin Meijboom <robin@meijboom.info>,
Borislav Petkov <bp@alien8.de>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] objtool: move stack-validation.txt to Documentation/
Date: Tue, 5 Mar 2019 07:44:13 -0700 [thread overview]
Message-ID: <20190305074413.5f72ecc1@lwn.net> (raw)
In-Reply-To: <1551764896-8453-2-git-send-email-yamada.masahiro@socionext.com>
On Tue, 5 Mar 2019 14:48:15 +0900
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> Move the document to the standard Documentation/ directory instead of
> creating the same directory structure under objtool/.
This seems like a good idea to me, but can I make a couple of requests?
- Convert it to RST while you're at it? It's 99% there already.
- Let's not add it to the top-level Documentation/ mess; I'm slowly
trying to bring some order there. Perhaps a better home would be
Documentation/kbuild/ ?
Thanks,
jon
next prev parent reply other threads:[~2019-03-05 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 5:48 [PATCH 1/3] tools: move initial declarations out of 'for' loop Masahiro Yamada
2019-03-05 5:48 ` [PATCH 2/3] objtool: move stack-validation.txt to Documentation/ Masahiro Yamada
2019-03-05 14:44 ` Jonathan Corbet [this message]
2019-03-05 5:48 ` [PATCH 3/3] objtool: move tools/objtool/ to scripts/objtool/ Masahiro Yamada
2019-03-05 14:46 ` Josh Poimboeuf
2019-03-05 16:08 ` Masahiro Yamada
2019-03-05 16:36 ` Josh Poimboeuf
2019-03-05 16:59 ` Peter Zijlstra
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=20190305074413.5f72ecc1@lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--cc=dianders@chromium.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=robin@meijboom.info \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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