From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yongseok Koh Subject: [PATCH v2] doc: fix a link in contribution guide Date: Fri, 6 Jan 2017 14:40:10 -0800 Message-ID: <20170106224010.24752-1-yskoh@mellanox.com> References: <20170106012232.20246-1-yskoh@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain Cc: , Yongseok Koh To: Return-path: Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10051.outbound.protection.outlook.com [40.107.1.51]) by dpdk.org (Postfix) with ESMTP id 5CD342A58 for ; Fri, 6 Jan 2017 23:40:26 +0100 (CET) In-Reply-To: <20170106012232.20246-1-yskoh@mellanox.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" A referenced document in the Linux Kernel has been moved to a sub-directory. And kernel community has moved to RST/Sphinx. The links are replaced with HTML rendered links. Signed-off-by: Yongseok Koh --- doc/guides/contributing/patches.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index c7006c191..193889a89 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -7,7 +7,7 @@ This document outlines the guidelines for submitting code to DPDK. The DPDK development process is modelled (loosely) on the Linux Kernel development model so it is worth reading the Linux kernel guide on submitting patches: -`How to Get Your Change Into the Linux Kernel `_. +`How to Get Your Change Into the Linux Kernel `_. The rationale for many of the DPDK guidelines is explained in greater detail in the kernel guidelines. @@ -192,7 +192,7 @@ Here are some guidelines for the body of a commit message: git commit --signoff # or -s The purpose of the signoff is explained in the - `Developer's Certificate of Origin `_ + `Developer's Certificate of Origin `_ section of the Linux kernel guidelines. .. Note:: -- 2.11.0