From: Mark Brown <broonie@kernel.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
corbet@lwn.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] docs/arm64: elf_hwcaps: unify newlines in HWCAP lists
Date: Thu, 18 Aug 2022 18:17:59 +0100 [thread overview]
Message-ID: <Yv50RxlDf0qpK9v8@sirena.org.uk> (raw)
In-Reply-To: <2bac83ef-d5a9-b8c4-0fb3-cef4272e7156@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Mon, Aug 15, 2022 at 03:37:58PM +0200, Martin Liška wrote:
> In git revision 94bdaa7d9a9d778d893c670d494c06d8e007c1cd I unified
> vertical spaces in a list of features.
The normal way of describing commits in a human readable fashion is to
include their title as is done in Fixes: tags.
> Since the revision, another commits added new features that have a different
> horizontal spacing.
> Fix these extra newlines.
This new format .rst is forcing does seem less than ideal for people
reading the actual file but oh well
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-18 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:19 [PATCH] docs/arm64: elf_hwcaps: Unify HWCAP lists as description lists Martin Liška
2022-08-15 13:00 ` Mark Brown
2022-08-15 13:37 ` [PATCH v2] docs/arm64: elf_hwcaps: unify newlines in HWCAP lists Martin Liška
2022-08-18 17:17 ` Mark Brown [this message]
2022-08-18 20:31 ` [PATCH v3] " Martin Liška
2022-08-23 11:34 ` Will Deacon
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=Yv50RxlDf0qpK9v8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mliska@suse.cz \
/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
all inboxes | Powered by JetHome®