From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: 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 08/11] docs: refcount-vs-atomic.rst: prefix url with https
Date: Wed, 9 May 2018 15:43:19 +0200 [thread overview]
Message-ID: <20180509134319.GA14921@andrea> (raw)
In-Reply-To: <d5683242124d6070c9a2d665c59e274d94c8b3ba.1525870886.git.mchehab+samsung@kernel.org>
Hi Mauro,
On Wed, May 09, 2018 at 10:18:51AM -0300, Mauro Carvalho Chehab wrote:
> There's a github URL there, but it is not prefixed by https.
> Add a prefix, to avoid false-positives with:
> ./scripts/documentation-file-ref-check
>
> As a side effect, Sphinx should also generate a cross-ref.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
There seems to be a "conflicting" patch ("applied" according to Jon):
http://lkml.kernel.org/r/1525468309-5310-1-git-send-email-andrea.parri@amarulasolutions.com
Let me stress here that the github repo. is out-of-date (and we have
no plans to keep that in sync with mainline).
Andrea
> ---
> Documentation/core-api/refcount-vs-atomic.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/refcount-vs-atomic.rst b/Documentation/core-api/refcount-vs-atomic.rst
> index 83351c258cdb..185d659e350a 100644
> --- a/Documentation/core-api/refcount-vs-atomic.rst
> +++ b/Documentation/core-api/refcount-vs-atomic.rst
> @@ -17,7 +17,7 @@ in order to help maintainers validate their code against the change in
> these memory ordering guarantees.
>
> The terms used through this document try to follow the formal LKMM defined in
> -github.com/aparri/memory-model/blob/master/Documentation/explanation.txt
> +https://github.com/aparri/memory-model/blob/master/Documentation/explanation.txt
>
> memory-barriers.txt and atomic_t.txt provide more background to the
> memory ordering in general and for atomic operations specifically.
> --
> 2.17.0
>
--
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
next prev parent reply other threads:[~2018-05-09 13:43 UTC|newest]
Thread overview: 22+ 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 ` [PATCH v2 01/11] docs: can.rst: fix a footnote reference Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 02/11] docs: admin-guide: add cgroup-v2 documentation Mauro Carvalho Chehab
2018-05-10 18:40 ` Tejun Heo
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 ` [PATCH v2 04/11] docs: dell_rbu.txt: fix location of request_firmware 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 ` [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 ` [PATCH v2 07/11] docs: ranoops.rst: fix location of ramoops.txt 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:43 ` Andrea Parri [this message]
2018-05-09 14:40 ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 10/11] arch/*: Kconfig: fix documentation for NMI watchdog 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 19:22 ` James Morris
2018-05-15 10:28 ` Bartlomiej Zolnierkiewicz
2018-05-15 14:52 ` Steven Rostedt
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 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=20180509134319.GA14921@andrea \
--to=andrea.parri@amarulasolutions.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 \
/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).