From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
gregkh@linuxfoundation.org
Subject: [PATCH 0/2] Report warnings to the file they belong
Date: Fri, 21 Jun 2019 12:28:00 -0300 [thread overview]
Message-ID: <cover.1561130657.git.mchehab+samsung@kernel.org> (raw)
Reporting an ABI error to the get_abi.pl script is not nice, as it
doesn't maky any easy to fix it.
Instead, just like with kernel-doc, put the fingers to the files
that didn't parse ok:
Documentation/ABI/testing/sysfs-kernel-mm-hugepages:3: WARNING: Definition list ends without a blank line; unexpected unindent.
Documentation/ABI/testing/evm:4: ERROR: Unexpected indentation.
Documentation/ABI/testing/evm:3: WARNING: Block quote ends without a blank line; unexpected unindent.
---
Greg,
Independently of the RFC patches, I would apply those two ones
together with the script, as they make a lot easier to debug
issues.
Mauro Carvalho Chehab (2):
get_abi.pl: Allow optionally record from where a line came from
docs: kernel_abi.py: use --enable-lineno for get_abi.pl
Documentation/sphinx/kernel_abi.py | 18 ++++++++++++++----
scripts/get_abi.pl | 21 ++++++++++++++++++++-
2 files changed, 34 insertions(+), 5 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-21 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 15:28 Mauro Carvalho Chehab [this message]
2019-06-21 15:28 ` [PATCH 1/2] get_abi.pl: Allow optionally record from where a line came from Mauro Carvalho Chehab
2019-06-21 15:28 ` [PATCH 2/2] docs: kernel_abi.py: use --enable-lineno for get_abi.pl Mauro Carvalho Chehab
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=cover.1561130657.git.mchehab+samsung@kernel.org \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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