public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Harry Wei <harryxiyou@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@zh-kernel.org
Subject: [PATCH 6/8] Documentation/sparse: drop __CHECK_ENDIAN__
Date: Thu, 15 Dec 2016 07:15:25 +0200	[thread overview]
Message-ID: <1481778865-27667-7-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1481778865-27667-1-git-send-email-mst@redhat.com>

It's no longer used.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 Documentation/translations/zh_CN/sparse.txt | 7 +------
 Documentation/dev-tools/sparse.rst          | 7 +------
 2 files changed, 2 insertions(+), 12 deletions(-)

diff --git a/Documentation/translations/zh_CN/sparse.txt b/Documentation/translations/zh_CN/sparse.txt
index cc144e5..e41dc94 100644
--- a/Documentation/translations/zh_CN/sparse.txt
+++ b/Documentation/translations/zh_CN/sparse.txt
@@ -92,9 +92,4 @@ DaveJ 把每小时自动生成的 git 源码树 tar 包放在以下地址:
 如果你已经编译了内核,用后一种方式可以很快地检查整个源码树。
 
 make 的可选变量 CHECKFLAGS 可以用来向 sparse 工具传递参数。编译系统会自
-动向 sparse 工具传递 -Wbitwise 参数。你可以定义 __CHECK_ENDIAN__ 来进行
-大小尾检查。
-
-	make C=2 CHECKFLAGS="-D__CHECK_ENDIAN__"
-
-这些检查默认都是被关闭的,因为他们通常会产生大量的警告。
+动向 sparse 工具传递 -Wbitwise 参数。
diff --git a/Documentation/dev-tools/sparse.rst b/Documentation/dev-tools/sparse.rst
index e08e6a8..78aa00a 100644
--- a/Documentation/dev-tools/sparse.rst
+++ b/Documentation/dev-tools/sparse.rst
@@ -102,9 +102,4 @@ be recompiled or not.  The latter is a fast way to check the whole tree if you
 have already built it.
 
 The optional make variable CF can be used to pass arguments to sparse.  The
-build system passes -Wbitwise to sparse automatically.  To perform endianness
-checks, you may define __CHECK_ENDIAN__::
-
-        make C=2 CF="-D__CHECK_ENDIAN__"
-
-These checks are disabled by default as they generate a host of warnings.
+build system passes -Wbitwise to sparse automatically.
-- 
MST

  parent reply	other threads:[~2016-12-15  5:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  5:15 [PATCH 0/8] enable endian checks for all sparse builds Michael S. Tsirkin
2016-12-15  5:15 ` [PATCH 1/8] linux/types.h: " Michael S. Tsirkin
2016-12-15  5:15 ` [PATCH 2/8] tools: " Michael S. Tsirkin
2016-12-15  5:15 ` [PATCH 3/8] Documentation/sparse: drop __bitwise__ Michael S. Tsirkin
2016-12-15  5:15 ` [PATCH 4/8] checkpatch: replace __bitwise__ with __bitwise Michael S. Tsirkin
2016-12-15 15:22   ` Joe Perches
2016-12-15  5:15 ` [PATCH 5/8] linux: drop __bitwise__ everywhere Michael S. Tsirkin
2016-12-15  9:04   ` Stefan Schmidt
2016-12-15 11:51   ` Greg Kroah-Hartman
2016-12-15 17:28   ` Krzysztof Kozlowski
2016-12-15 19:44   ` Lee Duncan
2016-12-19  9:09   ` Luca Coelho
2016-12-15  5:15 ` Michael S. Tsirkin [this message]
2016-12-15  5:15 ` [PATCH 7/8] fs/logfs: drop __CHECK_ENDIAN__ Michael S. Tsirkin
2016-12-15  5:15 ` [PATCH 8/8] Makefile: drop -D__CHECK_ENDIAN__ from cflags Michael S. Tsirkin
2016-12-15  7:00   ` Marcel Holtmann
2016-12-15  7:57   ` Marc Kleine-Budde
2016-12-15 11:50   ` Greg Kroah-Hartman
2016-12-15 20:15   ` Arend Van Spriel
2016-12-19  9:08   ` Luca Coelho

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=1481778865-27667-7-git-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=corbet@lwn.net \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kernel@zh-kernel.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