linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Lubomir Rintel <lkundrak@v3.sk>, Maen Suleiman <maen@marvell.com>,
	Lior Amsalem <alior@marvell.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	Eric Miao <eric.y.miao@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] docs: arm: marvell: drop some dead links
Date: Thu, 4 Feb 2021 22:57:59 +0100	[thread overview]
Message-ID: <YBxt57h+dOl7grza@lunn.ch> (raw)
In-Reply-To: <87pn1ffro8.fsf@meer.lwn.net>

On Thu, Feb 04, 2021 at 02:29:11PM -0700, Jonathan Corbet wrote:
> Lubomir Rintel <lkundrak@v3.sk> writes:
> 
> > Just remove these; there's good chance there wasn't anything useful
> > there anyway.
> >
> > Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> >
> > ---
> > Changes since v1:
> > - Adjust for removal of "[PATCH 1/5] docs: arm: marvell: turn the automatic
> >   links into labels"
> > - Split off the hunk that fixes 38x functional spec link
> >
> >  Documentation/arm/marvel.rst | 25 -------------------------
> >  1 file changed, 25 deletions(-)
> >
> > diff --git a/Documentation/arm/marvel.rst b/Documentation/arm/marvel.rst
> > index 16ab2eb085b86..502a1b89a2c85 100644
> > --- a/Documentation/arm/marvel.rst
> > +++ b/Documentation/arm/marvel.rst
> > @@ -63,8 +63,6 @@ Kirkwood family
> >                  - Product Brief  : http://www.marvell.com/embedded-processors/kirkwood/assets/88F6281-004_ver1.pdf
> >                  - Hardware Spec  : http://www.marvell.com/embedded-processors/kirkwood/assets/HW_88F6281_OpenSource.pdf
> >                  - Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_OpenSource.pdf
> > -  Homepage:
> > -	http://www.marvell.com/embedded-processors/kirkwood/
> >    Core:
> >  	Feroceon 88fr131 ARMv5 compatible
> >    Linux kernel mach directory:
> > @@ -126,7 +124,6 @@ EBU Armada family
> >  	- 88F6820 Armada 385
> >  	- 88F6828 Armada 388
> >  
> > -    - Product infos:   http://www.marvell.com/embedded-processors/armada-38x/
> 
> So these URLs do still exist in the Wayback machine; the above is
> https://web.archive.org/web/20180829171124/http://www.marvell.com/embedded-processors/armada-38x/
> for example.  If we delete the links, we make it harder for any
> interested person to ever find them.  Assuming that we want to keep
> information about these product families in the documentation at all,
> I'd think that we would want to have the online information as well.  So
> I'd replace these with wayback links, or else just leave them as they
> are so that sufficiently motivated people can look them up themselves...

The kirkwood processors are old, but they were used in NAS
devices. They tend to have a long life time, and people do put Debian
on them. Armada-38x is definitely still in use in NAS boxes.

If we can have working links, that would be great.

   Andrew

  reply	other threads:[~2021-02-04 21:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 23:53 [PATCH v2 0/5] docs: arm: Improvements to Marvell SoC documentation Lubomir Rintel
2021-02-03 23:53 ` [PATCH v2 1/5] docs: arm: marvell: drop some dead links Lubomir Rintel
2021-02-04 21:29   ` Jonathan Corbet
2021-02-04 21:57     ` Andrew Lunn [this message]
2021-02-03 23:53 ` [PATCH v2 2/5] docs: arm: marvell: fix 38x functional spec link Lubomir Rintel
2021-02-03 23:53 ` [PATCH v2 3/5] docs: arm: marvell: replace stale links with archive links Lubomir Rintel
2021-02-03 23:53 ` [PATCH v2 4/5] docs: arm: marvell: clarify some unimportant Armada 6x0 details Lubomir Rintel
2021-02-03 23:53 ` [PATCH v2 5/5] docs: arm: marvell: rename marvel.rst to marvell.rst Lubomir Rintel
2021-02-04 21:31   ` Jonathan Corbet
2021-02-04 21:32 ` [PATCH v2 0/5] docs: arm: Improvements to Marvell SoC documentation Jonathan Corbet

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=YBxt57h+dOl7grza@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alior@marvell.com \
    --cc=corbet@lwn.net \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=maen@marvell.com \
    --cc=nico@fluxnic.net \
    --cc=thomas.petazzoni@free-electrons.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).