From: Matthew Wilcox <willy@infradead.org>
To: Cristian Souza <cristianmsbr@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH v2] docs: admin-guide: Clarify sentences
Date: Thu, 9 Apr 2020 11:13:11 -0700 [thread overview]
Message-ID: <20200409181311.GW21484@bombadil.infradead.org> (raw)
In-Reply-To: <20200408144653.GA123268@darkstar>
On Wed, Apr 08, 2020 at 11:46:53AM -0300, Cristian Souza wrote:
> @@ -1,34 +1,30 @@
> -Explaining the dreaded "No working init found." boot hang message
> -=================================================================
> +Explaining the "No working init found." boot hang message
> +=========================================================
>
> -OK, so you have got this pretty unintuitive message (currently located
> -in init/main.c) and are wondering what went wrong.
> -Some high-level reasons for failure (listed roughly in order of execution)
> -to load the init binary are:
> +Message location: ``init/main.c``
I don't think this should be the first paragraph ;-)
Maybe just skip it altogether? The sysadmin doesn't care where the
message is located.
> +5) **Binary cannot be loaded**: Make sure the binary's architecture matches your hardware.
Line exceeds 80 characters (other occurrences of this)
> e.g. by providing additional error messages at affected places.
>
> Andreas Mohr <andi at lisas period de>
> +Cristian Souza <cristianmsbr at gmail period com>
We tend to use :Author: at the top of the file instead of signatories at the
bottom.
next prev parent reply other threads:[~2020-04-09 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 14:46 [PATCH v2] docs: admin-guide: Clarify sentences Cristian Souza
2020-04-09 18:13 ` Matthew Wilcox [this message]
2020-04-09 19:46 ` Cristian Souza
2020-04-10 16:18 ` Jonathan Corbet
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=20200409181311.GW21484@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=cristianmsbr@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).