DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 3/3] doc: removed intel blurb from linux gsg
Date: Fri, 19 Dec 2014 15:08:48 +0000	[thread overview]
Message-ID: <1419001728-7878-4-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <1419001728-7878-1-git-send-email-pablo.de.lara.guarch@intel.com>

Removed redundant Intel legal blurb from linux gsg.

Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
 doc/guides/linux_gsg/index.rst | 38 --------------------------------------
 1 file changed, 38 deletions(-)

diff --git a/doc/guides/linux_gsg/index.rst b/doc/guides/linux_gsg/index.rst
index 8dc3e48..ab07ea2 100644
--- a/doc/guides/linux_gsg/index.rst
+++ b/doc/guides/linux_gsg/index.rst
@@ -33,44 +33,6 @@ Getting Started Guide for Linux
 
 |today|
 
-INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS.
-NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
-EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
-RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT,
-COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
-
-A “Mission Critical Application” is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death.
-SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES,
-AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY,
-ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR
-ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
-
-Intel may make changes to specifications and product descriptions at any time, without notice.
-Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.”
-Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
-The information here is subject to change without notice. Do not finalize a design with this information.
-
-The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications.
-Current characterized errata are available on request.
-
-Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
-
-Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725,
-or go to: http://www.intel.com/design/literature.htm
-
-Any software source code reprinted in this document is furnished for informational purposes only and may only be used or copied and no license,
-express or implied, by estoppel or otherwise, to any of the reprinted source code is granted by this document.
-
-Code Names are only for use by Intel to identify products, platforms, programs, services, etc. (“products”) in development by Intel
-that have not been made commercially available to the public, i.e., announced, launched or shipped.
-They are never to be used as “commercial” names for products. Also, they are not intended to function as trademarks.
-
-Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.
-
-\*Other names and brands may be claimed as the property of others.
-
-Copyright © 2012-2014, Intel Corporation. All rights reserved.
-
 Contents
 
 .. toctree::
-- 
2.1.0

  parent reply	other threads:[~2014-12-19 15:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 23:41 [dpdk-dev] [PATCH 0/2] doc: update to i40e enabling and gsg fixes Siobhan Butler
2014-12-02 23:41 ` [dpdk-dev] [PATCH 1/2] doc: updated i40e enabling additonal fnct in gsg Siobhan Butler
2014-12-03 11:41   ` Iremonger, Bernard
2014-12-02 23:41 ` [dpdk-dev] [PATCH 2/2] doc: remove references to intel dpdk in linux_gsg Siobhan Butler
2014-12-03 11:43   ` Iremonger, Bernard
2014-12-03 13:26   ` Thomas Monjalon
2014-12-19 15:08 ` [dpdk-dev] [PATCH v2 0/3] update to i40e enabling and gsg fixes Pablo de Lara
2014-12-19 15:08   ` [dpdk-dev] [PATCH v2 1/3] doc: updated i40e enabling additonal fnct in gsg Pablo de Lara
2014-12-19 16:00     ` Iremonger, Bernard
2014-12-19 21:42     ` Thomas Monjalon
2014-12-19 15:08   ` [dpdk-dev] [PATCH v2 2/3] doc: remove references to intel dpdk in linux_gsg Pablo de Lara
2014-12-19 16:01     ` Iremonger, Bernard
2014-12-19 15:08   ` Pablo de Lara [this message]
2014-12-19 16:01     ` [dpdk-dev] [PATCH v2 3/3] doc: removed intel blurb from linux gsg Iremonger, Bernard

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=1419001728-7878-4-git-send-email-pablo.de.lara.guarch@intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.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).