All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Parri <parri.andrea@gmail.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2 09/11] docs: Fix some broken references
Date: Thu, 14 Jun 2018 17:01:07 +0200	[thread overview]
Message-ID: <20180614150107.GA21191@andrea> (raw)
In-Reply-To: <20180614112343.61bb84d7@coco.lan>

On Thu, Jun 14, 2018 at 11:23:43AM -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 9 May 2018 15:11:07 -0400 (EDT)
> Alan Stern <stern@rowland.harvard.edu> escreveu:
> 
> > On Wed, 9 May 2018, Mauro Carvalho Chehab wrote:
> > 
> > > Em Wed, 9 May 2018 19:15:01 +0200
> > > Andrea Parri <parri.andrea@gmail.com> escreveu:  
> > 
> > > > >  tools/memory-model/README                     | 10 +++++-----    
> > > > 
> > > > As mentioned in the previous thread, I am for keeping the current
> > > > references: the REAMDE is listing the doc files, as well as other
> > > > files in tools/memory-model/, relatively to that directory.  
> > > 
> > > Yeah, at least this hunk deserves some rework, as now some
> > > references are Documentation/.../foo, while others are just
> > > bar.
> > > 
> > > As on (almost) all other places (except for tools/memory-model/README),
> > > the references are always from the main directory, I would make all
> > > patches there also relative to main dir. If you're afraid of
> > > not being too clearer, we could prefix all of them with something
> > > like:
> > > 
> > > 	${LINUX}/tools/memory-model/...
> > > 
> > > just like some DT binding files do:
> > > 
> > > 	Documentation/devicetree/bindings/sound/audio-graph-card.txt:see ${LINUX}/Documentation/devicetree/bindings/graph.txt
> > > 
> > > A bonus of doing that is that the broken reference detect script can
> > > keep parsing it without changes (well, it wouldn't be hard to make
> > > it also accept a relative file, but doing that just due to 
> > > tools/memory-model/README seems overkill).
> > > 
> > > Another advantage is that it would allow to easily add references
> > > there from the main kernel Documentation, if needed in the future,
> > > without messing with local x non-local relative namespace.  
> > 
> > How about changing the relative references so that something like
> > Documentation/recipes.txt becomes ./Documentation/recipes.txt?
> 
> Thanks,
> Mauro
> 
> After thinking a little bit about that, it should be easy to fix the
> tool to consider references relative to tools/.*/Documentation.
> 
> I intend to send a new patch series with the changes to 
> tools/memory-model/README removed from this patch and with the enclosed
> patch on it.

LGTM,  thanks!

  Andrea


> 
> Regards,
> Mauro
> 
> [PATCH] scripts/documentation-file-ref-check: check
>  tools/*/Documentation
> 
> Some files, like tools/memory-model/README has references to
> a Documentation file that is locale to it. Handle references
> that are relative to them too.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> 
> diff --git a/scripts/documentation-file-ref-check b/scripts/documentation-file-ref-check
> index 047f463cdf4b..078999a3fdff 100755
> --- a/scripts/documentation-file-ref-check
> +++ b/scripts/documentation-file-ref-check
> @@ -78,6 +78,13 @@ while (<IN>) {
>  		# Check if exists, evaluating wildcards
>  		next if (grep -e, glob("$ref $fulref"));
>  
> +		# Accept relative Documentation patches for tools/
> +		if ($f =~ m/tools/) {
> +			my $path = $f;
> +			$path =~ s,(.*)/.*,$1,;
> +			next if (grep -e, glob("$path/$ref $path/$fulref"));
> +		}
> +
>  		if ($fix) {
>  			if (!($ref =~ m/(scripts|Kconfig|Kbuild)/)) {
>  				$broken_ref{$ref}++;
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Andrea Parri <parri.andrea@gmail.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2 09/11] docs: Fix some broken references
Date: Thu, 14 Jun 2018 17:01:07 +0200	[thread overview]
Message-ID: <20180614150107.GA21191@andrea> (raw)
In-Reply-To: <20180614112343.61bb84d7@coco.lan>

On Thu, Jun 14, 2018 at 11:23:43AM -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 9 May 2018 15:11:07 -0400 (EDT)
> Alan Stern <stern@rowland.harvard.edu> escreveu:
> 
> > On Wed, 9 May 2018, Mauro Carvalho Chehab wrote:
> > 
> > > Em Wed, 9 May 2018 19:15:01 +0200
> > > Andrea Parri <parri.andrea@gmail.com> escreveu:  
> > 
> > > > >  tools/memory-model/README                     | 10 +++++-----    
> > > > 
> > > > As mentioned in the previous thread, I am for keeping the current
> > > > references: the REAMDE is listing the doc files, as well as other
> > > > files in tools/memory-model/, relatively to that directory.  
> > > 
> > > Yeah, at least this hunk deserves some rework, as now some
> > > references are Documentation/.../foo, while others are just
> > > bar.
> > > 
> > > As on (almost) all other places (except for tools/memory-model/README),
> > > the references are always from the main directory, I would make all
> > > patches there also relative to main dir. If you're afraid of
> > > not being too clearer, we could prefix all of them with something
> > > like:
> > > 
> > > 	${LINUX}/tools/memory-model/...
> > > 
> > > just like some DT binding files do:
> > > 
> > > 	Documentation/devicetree/bindings/sound/audio-graph-card.txt:see ${LINUX}/Documentation/devicetree/bindings/graph.txt
> > > 
> > > A bonus of doing that is that the broken reference detect script can
> > > keep parsing it without changes (well, it wouldn't be hard to make
> > > it also accept a relative file, but doing that just due to 
> > > tools/memory-model/README seems overkill).
> > > 
> > > Another advantage is that it would allow to easily add references
> > > there from the main kernel Documentation, if needed in the future,
> > > without messing with local x non-local relative namespace.  
> > 
> > How about changing the relative references so that something like
> > Documentation/recipes.txt becomes ./Documentation/recipes.txt?
> 
> Thanks,
> Mauro
> 
> After thinking a little bit about that, it should be easy to fix the
> tool to consider references relative to tools/.*/Documentation.
> 
> I intend to send a new patch series with the changes to 
> tools/memory-model/README removed from this patch and with the enclosed
> patch on it.

LGTM,  thanks!

  Andrea


> 
> Regards,
> Mauro
> 
> [PATCH] scripts/documentation-file-ref-check: check
>  tools/*/Documentation
> 
> Some files, like tools/memory-model/README has references to
> a Documentation file that is locale to it. Handle references
> that are relative to them too.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> 
> diff --git a/scripts/documentation-file-ref-check b/scripts/documentation-file-ref-check
> index 047f463cdf4b..078999a3fdff 100755
> --- a/scripts/documentation-file-ref-check
> +++ b/scripts/documentation-file-ref-check
> @@ -78,6 +78,13 @@ while (<IN>) {
>  		# Check if exists, evaluating wildcards
>  		next if (grep -e, glob("$ref $fulref"));
>  
> +		# Accept relative Documentation patches for tools/
> +		if ($f =~ m/tools/) {
> +			my $path = $f;
> +			$path =~ s,(.*)/.*,$1,;
> +			next if (grep -e, glob("$path/$ref $path/$fulref"));
> +		}
> +
>  		if ($fix) {
>  			if (!($ref =~ m/(scripts|Kconfig|Kbuild)/)) {
>  				$broken_ref{$ref}++;

  reply	other threads:[~2018-06-14 15:01 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 13:18 [PATCH v2 00/11] Fix some doc build warnings/errors and broken links Mauro Carvalho Chehab
2018-05-09 13:18 ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 01/11] docs: can.rst: fix a footnote reference Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 02/11] docs: admin-guide: add cgroup-v2 documentation Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-10 18:40   ` Tejun Heo
2018-05-10 18:40     ` Tejun Heo
2018-05-10 20:02     ` Jonathan Corbet
2018-05-10 20:02       ` Jonathan Corbet
2018-05-09 13:18 ` [PATCH v2 03/11] docs: crypto_engine.rst: Fix two parse warnings Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 04/11] docs: dell_rbu.txt: fix location of request_firmware Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 15:06   ` Mauro Carvalho Chehab
2018-05-09 15:06     ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 05/11] docs: uio-howto.rst: use a code block to solve a warning Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 06/11] scripts/documentation-file-ref-check: rewrite it in perl with auto-fix mode Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 07/11] docs: ranoops.rst: fix location of ramoops.txt Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 08/11] docs: refcount-vs-atomic.rst: prefix url with https Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:43   ` Andrea Parri
2018-05-09 13:43     ` Andrea Parri
2018-05-09 14:40     ` Mauro Carvalho Chehab
2018-05-09 14:40       ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 09/11] docs: Fix some broken references Mauro Carvalho Chehab
2018-05-09 13:18 ` Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 17:15   ` Andrea Parri
2018-05-09 17:15     ` Andrea Parri
2018-05-09 17:15     ` Andrea Parri
2018-05-09 18:20     ` Mauro Carvalho Chehab
2018-05-09 18:20       ` Mauro Carvalho Chehab
2018-05-09 18:20       ` Mauro Carvalho Chehab
2018-05-09 19:11       ` Alan Stern
2018-05-09 19:11         ` Alan Stern
2018-05-09 19:11         ` Alan Stern
2018-05-09 19:41         ` Mauro Carvalho Chehab
2018-05-09 19:41           ` Mauro Carvalho Chehab
2018-05-09 19:41           ` Mauro Carvalho Chehab
2018-05-09 21:27           ` Andrea Parri
2018-05-09 21:27             ` Andrea Parri
2018-05-09 21:27             ` Andrea Parri
2018-05-09 19:41         ` Mauro Carvalho Chehab
2018-06-14 14:23         ` Mauro Carvalho Chehab
2018-06-14 14:23           ` Mauro Carvalho Chehab
2018-06-14 15:01           ` Andrea Parri [this message]
2018-06-14 15:01             ` Andrea Parri
2018-05-09 19:20       ` Andrea Parri
2018-05-09 19:20         ` Andrea Parri
2018-05-09 19:20         ` Andrea Parri
2018-05-09 18:20     ` Mauro Carvalho Chehab
2018-05-13  7:13   ` Takashi Iwai
2018-05-13  7:13   ` Takashi Iwai
2018-05-13  7:13     ` Takashi Iwai
2018-05-13  7:13     ` Takashi Iwai
2018-05-14 13:31   ` Masami Hiramatsu
2018-05-14 13:31   ` Masami Hiramatsu
2018-05-14 13:31     ` Masami Hiramatsu
2018-05-14 13:31     ` Masami Hiramatsu
2018-05-15 20:26   ` Stephen Boyd
2018-05-15 20:26     ` Stephen Boyd
2018-05-15 20:26     ` Stephen Boyd
2018-05-15 20:26     ` Stephen Boyd
2018-05-15 20:26     ` Stephen Boyd
2018-05-16  9:09   ` Charles Keepax
2018-05-16  9:09     ` Charles Keepax
2018-05-16  9:09     ` Charles Keepax
2018-05-16 15:12   ` Mathieu Poirier
2018-05-16 15:12     ` Mathieu Poirier
2018-05-16 15:12     ` Mathieu Poirier
2018-05-09 13:18 ` [PATCH v2 10/11] arch/*: Kconfig: fix documentation for NMI watchdog Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 11/11] docs: fix broken references with multiple hints Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18   ` [v2,11/11] " Mauro Carvalho Chehab
2018-05-09 13:18   ` [PATCH v2 11/11] " Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 13:18   ` Mauro Carvalho Chehab
2018-05-09 19:22   ` James Morris
2018-05-09 19:22     ` James Morris
2018-05-09 19:22     ` [v2,11/11] " James Morris
2018-05-09 19:22     ` [PATCH v2 11/11] " James Morris
2018-05-09 19:22     ` James Morris
2018-05-09 19:22     ` James Morris
2018-05-15 10:28   ` Bartlomiej Zolnierkiewicz
2018-05-15 10:28     ` Bartlomiej Zolnierkiewicz
2018-05-15 10:28     ` [v2,11/11] " Bartlomiej Zolnierkiewicz
2018-05-15 10:28     ` [PATCH v2 11/11] " Bartlomiej Zolnierkiewicz
2018-05-15 10:28     ` Bartlomiej Zolnierkiewicz
2018-05-15 10:28     ` Bartlomiej Zolnierkiewicz
2018-05-15 14:52   ` Steven Rostedt
2018-05-15 14:52     ` Steven Rostedt
2018-05-15 14:52     ` [v2,11/11] " Steven Rostedt
2018-05-15 14:52     ` [PATCH v2 11/11] " Steven Rostedt
2018-05-15 14:52     ` Steven Rostedt
2018-05-15 14:52     ` Steven Rostedt
2018-05-22 17:31   ` Rob Herring
2018-05-22 17:31     ` Rob Herring
2018-05-22 17:31     ` [v2,11/11] " Rob Herring
2018-05-22 17:31     ` [PATCH v2 11/11] " Rob Herring
2018-05-22 17:31     ` Rob Herring
2018-05-22 17:31     ` Rob Herring
2018-05-10 20:22 ` [PATCH v2 00/11] Fix some doc build warnings/errors and broken links Jonathan Corbet
2018-05-10 20:22   ` Jonathan Corbet
2018-05-10 21:28   ` Mauro Carvalho Chehab
2018-05-10 21:28     ` 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=20180614150107.GA21191@andrea \
    --to=parri.andrea@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=mchehab@infradead.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.