From patchwork Wed Aug 1 17:28:48 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?b?TcOhdMOpIEVja2w=?= X-Patchwork-Id: 952312 X-Patchwork-Delegate: pablo@netfilter.org Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=netfilter-devel-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="ijZ9ZoC5"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 41ggK16my3z9sCX for ; Thu, 2 Aug 2018 03:29:09 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2407536AbeHATPv (ORCPT ); Wed, 1 Aug 2018 15:15:51 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:46267 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2407064AbeHATPu (ORCPT ); Wed, 1 Aug 2018 15:15:50 -0400 Received: by mail-wr1-f68.google.com with SMTP id h14-v6so20900526wrw.13 for ; Wed, 01 Aug 2018 10:29:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=qw5G4lNlIZKXSuTcaQfUO0YBF5MrSi5zJPcKjBTBZhc=; b=ijZ9ZoC5c/AeswLDqdAujkFCXOmYyLbE22Y4jiM04JEy+M9xF2YsaUwzjIAI6ZG9Ve bFeu/LHjfdurQd+/hy2y+G/xlZ4OSczsp4wh8hZ2W+pOKYw3k5+WddK4W/qedYysQrmd uebL7uhTXS4CW1Lr/2UmCQtAifgWJZRZH+xH5c6p7goBgGIs/+RDgKVAia1oX+F8S4Yn MFdgXEBsDe0+DK66IkSOwhtScoNgRx+6CyGW7lRrkPR9ORcWiS33o2KzuxuoRj9EcMvT qUR+BMH8geV2batzIvTQFpxOYvXEFYkHystH7+UIha21iSbIXWusevTepN7RkYfw8Yly TsRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=qw5G4lNlIZKXSuTcaQfUO0YBF5MrSi5zJPcKjBTBZhc=; b=fTV3aDLKcGoEZz8whPBHGDy20Iz8mqwr8pUUIcBsC/aXl+PXeDNPoYn7HQYe20S3rQ sQIbVLjxy7Tjyx8B/Oeb+ZksDsmN1in8fuD3mCA0BTo0O+o8Kl+a7D93NjmYcoHXWVRT ynieei438+8f5evm+AZ/p7krYZjDB5v3UcxYDQ5UMD2hmYwUPnnRWhOOYftbNU8y2PPp XhekyH2U01LmbZScuLxlt1zn0VLdzafTMJ0/Wo1lmz3C3jNEvu7jONpGju0NiLUayNyf 8i/De3sDuLFif5DtRTOeLiVjTJ76jg1cWB7MxAzY5Nv7n8gI7rsLdfTzZnOao5LZHkXS 5QyA== X-Gm-Message-State: AOUpUlGIPpF+xH1iAwa6y4ft4XA2vpkJJyaAoxK1at/Vj6gdOW1a8yeL kWVr+jfFlr8yW99HZTLwoXpr7dDy X-Google-Smtp-Source: AAOMgpec/H72Z2GvUvCKHxi9JbIM4YuMMJhnkBk3I7f8L9BUMg5DO4wxvlzJ/4rWExEdlfg0ugDpgA== X-Received: by 2002:adf:94e2:: with SMTP id 89-v6mr24374375wrr.48.1533144545386; Wed, 01 Aug 2018 10:29:05 -0700 (PDT) Received: from ecklm-lapos.localdomain (ecklm-pi.sch.bme.hu. [152.66.179.182]) by smtp.gmail.com with ESMTPSA id s9-v6sm5156660wmc.34.2018.08.01.10.29.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Aug 2018 10:29:05 -0700 (PDT) From: =?utf-8?b?TcOhdMOpIEVja2w=?= To: netfilter-devel@vger.kernel.org Cc: arushisinghal19971997@gmail.com Subject: [PATCH nft 1/5] doc: data-types.txt: Wrap extra long lines to 80 chars Date: Wed, 1 Aug 2018 19:28:48 +0200 Message-Id: <559b1d5900fed93df4e6f51f6db493613bc81f6e.1533144099.git.ecklm94@gmail.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: References: MIME-Version: 1.0 Sender: netfilter-devel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org Signed-off-by: Máté Eckl --- doc/data-types.txt | 29 ++++++++++++++++++++++------- 1 file changed, 22 insertions(+), 7 deletions(-) diff --git a/doc/data-types.txt b/doc/data-types.txt index 1d4218e..57aa3a4 100644 --- a/doc/data-types.txt +++ b/doc/data-types.txt @@ -9,7 +9,9 @@ variable | - |=================== -The integer type is used for numeric values. It may be specified as decimal, hexadecimal or octal number. The integer type doesn't have a fixed size, its size is determined by the expression for which it is used. +The integer type is used for numeric values. It may be specified as decimal, +hexadecimal or octal number. The integer type doesn't have a fixed size, its +size is determined by the expression for which it is used. BITMASK TYPE ~~~~~~~~~~~~ @@ -35,7 +37,10 @@ variable | - |=================== -The string type is used for character strings. A string begins with an alphabetic character (a-zA-Z) followed by zero or more alphanumeric characters or the characters /, -, _ and .. In addition anything enclosed in double quotes (") is recognized as a string. +The string type is used for character strings. A string begins with an +alphabetic character (a-zA-Z) followed by zero or more alphanumeric characters +or the characters /, -, _ and .. In addition anything enclosed in double +quotes (") is recognized as a string. .String specification ---------------------- @@ -57,7 +62,9 @@ variable | integer |=================== -The link layer address type is used for link layer addresses. Link layer addresses are specified as a variable amount of groups of two hexadecimal digits separated using colons (:). +The link layer address type is used for link layer addresses. Link layer +addresses are specified as a variable amount of groups of two hexadecimal digits +separated using colons (:). .Link layer address specification ---------------------- @@ -76,7 +83,10 @@ ipv4_addr| integer |=================== -The IPv4 address type is used for IPv4 addresses. Addresses are specified in either dotted decimal, dotted hexadecimal, dotted octal, decimal, hexadecimal, octal notation or as a host name. A host name will be resolved using the standard system resolver. +The IPv4 address type is used for IPv4 addresses. Addresses are specified in +either dotted decimal, dotted hexadecimal, dotted octal, decimal, hexadecimal, +octal notation or as a host name. A host name will be resolved using the +standard system resolver. .IPv4 address specification ---------------------- @@ -98,7 +108,9 @@ ipv6_addr| integer |=================== -The IPv6 address type is used for IPv6 addresses. Addresses are specified as a host name or as hexadecimal halfwords separated by colons. Addresses might be enclosed in square brackets ("[]") to differentiate them from port numbers. +The IPv6 address type is used for IPv6 addresses. Addresses are specified as a +host name or as hexadecimal halfwords separated by colons. Addresses might be +enclosed in square brackets ("[]") to differentiate them from port numbers. .IPv6 address specificationIPv6 address specification with bracket notation ---------------------- @@ -120,7 +132,9 @@ boolean | integer |=================== -The boolean type is a syntactical helper type in user space. It's use is in the right-hand side of a (typically implicit) relational expression to change the expression on the left-hand side into a boolean check (usually for existence). + +The boolean type is a syntactical helper type in user space. It's use is in the +right-hand side of a (typically implicit) relational expression to change the +expression on the left-hand side into a boolean check (usually for existence). + The following keywords will automatically resolve into a boolean type with given value: The bitmask type (bitmask) is used for bitmasks. @@ -361,7 +375,8 @@ icmpv6_type | integer |=================== -The ICMPvX Code type abstraction is a set of values which overlap between ICMP and ICMPv6 Code types to be used from the inet family. +The ICMPvX Code type abstraction is a set of values which overlap between ICMP +and ICMPv6 Code types to be used from the inet family. .keywords may be used when specifying the ICMPvX code [options="header"]