From: Jonathan Corbet <corbet@lwn.net>
To: Gerald BAEZA <gerald.baeza@st.com>
Cc: Alexandre TORGUE <alexandre.torgue@st.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Documentation: add link to stm32mp157 docs
Date: Mon, 7 Oct 2019 09:32:08 -0600 [thread overview]
Message-ID: <20191007093208.757554b0@lwn.net> (raw)
In-Reply-To: <8d097a0486e94257952600bf6d20975d@SFHDAG5NODE1.st.com>
On Thu, 3 Oct 2019 10:05:46 +0000
Gerald BAEZA <gerald.baeza@st.com> wrote:
> > > Adding the URL is a fine idea. But you don't need the extra syntax to
> > > create a link if you're not going to actually make a link out of it.
> > > So I'd take the ".. _STM32MP157:" part out and life will be good.
> > >
> >
> > We also did it for older stm32 product. Idea was to not have the "full"
> > address but just a shortcut of the link when html file is read. It maybe makes
> > no sens ? (if yes we will have to update older stm32 overview :))
>
> Example in https://www.kernel.org/doc/html/latest/arm/stm32/stm32h743-overview.html
>
> Do you agree to continue like this ?
If you actually use the reference then it's OK, I guess; in the posted
document that wasn't happening. I still think it might be a bit more
straightforward to just put the URL; that will make the plain-text file a
little more readable. In the end, though, it's up to you, go with
whichever you prefer.
Thanks,
jon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-07 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 12:19 [PATCH] Documentation: add link to stm32mp157 docs Gerald BAEZA
2019-08-27 13:48 ` Jonathan Corbet
2019-08-27 15:23 ` Alexandre Torgue
2019-08-29 15:44 ` Jonathan Corbet
2019-10-03 10:05 ` Gerald BAEZA
2019-10-07 15:32 ` Jonathan Corbet [this message]
2019-10-08 9:19 ` Gerald BAEZA
2019-10-25 9:42 ` Alexandre Torgue
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=20191007093208.757554b0@lwn.net \
--to=corbet@lwn.net \
--cc=alexandre.torgue@st.com \
--cc=gerald.baeza@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
/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).