All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: replace broken specification URL
Date: Wed, 14 Sep 2016 13:00:07 -0400	[thread overview]
Message-ID: <yq1k2eemn6w.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <c7b4c63e-af53-401c-3854-d3edea258e53@free-electrons.com> (Michael Opdenacker's message of "Fri, 9 Sep 2016 10:16:46 +0200")

>>>>> "Michael" == Michael Opdenacker <michael.opdenacker@free-electrons.com> writes:

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.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2016-09-14 17:00 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 [this message]
2016-09-15 12:33       ` Michael Opdenacker
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=yq1k2eemn6w.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.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=michael.opdenacker@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 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.