linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 0/3] scripts: get_abi.pl: some additional fixes and doc update
Date: Mon, 27 Sep 2021 15:49:48 +0200	[thread overview]
Message-ID: <cover.1632750315.git.mchehab+huawei@kernel.org> (raw)

Hi Greg,

This small series address a couple of issues I noticed while testing it
on an arm64 board (HiKey970). Those are addressed on patches 1
and 2.

Patch 2 is the real fix: it prevents creating aliases for nodes that
are ignored (specially for /sys/firmware, where there's no documentation
for the files created there under Documentation/ABI - nor it makes
sense to have it).

Patch 1 prevents similar cases, as it will produce an error if a
symlink is pointing to an entry that was not added at the internal
representation of the sysfs.

Patch 3 just update a few things at the documentation inside the
script.

Mauro Carvalho Chehab (3):
  scripts: get_abi.pl: produce an error if the ref tree is broken
  scripts: get_abi.pl: fix parse logic for DT firmware
  scripts: get_abi.pl: update its documentation

 scripts/get_abi.pl | 70 +++++++++++++++++++++++++++++-----------------
 1 file changed, 45 insertions(+), 25 deletions(-)

-- 
2.31.1



             reply	other threads:[~2021-09-27 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 13:49 Mauro Carvalho Chehab [this message]
2021-09-27 13:49 ` [PATCH 1/3] scripts: get_abi.pl: produce an error if the ref tree is broken Mauro Carvalho Chehab
2021-09-27 13:49 ` [PATCH 2/3] scripts: get_abi.pl: fix parse logic for DT firmware Mauro Carvalho Chehab
2021-09-27 13:49 ` [PATCH 3/3] scripts: get_abi.pl: update its documentation 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.1632750315.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --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).