All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: Re: [PATCH] scsi: replace broken specification URL
Date: Thu, 15 Sep 2016 14:33:57 +0200	[thread overview]
Message-ID: <7884d730-1d65-73c0-b94d-196bda3211d5@free-electrons.com> (raw)
In-Reply-To: <yq1k2eemn6w.fsf@sermon.lab.mkp.net>

Hi Martin,

On 14/09/2016 19:00, Martin K. Petersen wrote:
>
> Michael> So, should we only that the cam-r12b document can be found from
> Michael> http://www.t10.org/t10docs.htm (registration required)?, and
> Michael> tell that a copy can be found on
> Michael> http://www.csit-sun.pub.ro/~cpop/Documentatie_SMP/Standarde_magistrale/SCSI/?
>
> As inconvenient as the T10/ANSI restrictions are, we should not be
> linking to illegitimate spec repositories.

I agree with you. The documents do not allow copy without permission, so 
the copies we found are illegitimate indeed.

Now I know what patch to send, to get rid of the broken link :)

Thanks,

Michael.

-- 
Michael Opdenacker, CEO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-15 12:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02  6:56 [PATCH] scsi: replace broken specification URL Michael Opdenacker
2016-07-02 14:49 ` James Bottomley
2016-09-09  8:16   ` Michael Opdenacker
2016-09-09 22:53     ` Tyrel Datwyler
2016-09-14 17:00     ` Martin K. Petersen
2016-09-15 12:33       ` Michael Opdenacker [this message]
2016-09-15 13:03         ` Michael Opdenacker
2016-09-15 14:06           ` Martin K. Petersen
2016-09-16  1:00             ` Laurence Oberman
2016-09-16  0:57           ` Laurence Oberman

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=7884d730-1d65-73c0-b94d-196bda3211d5@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.