Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2200909ybi; Sun, 9 Jun 2019 06:11:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqzvQtn+w4LTQI7RRtGMHxmU2j1ROgOBvuzdTo9tAcZrwD3BeMxddZ8fcLwjLmivhFBBVywC X-Received: by 2002:a17:902:aa0a:: with SMTP id be10mr58786866plb.27.1560085884825; Sun, 09 Jun 2019 06:11:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560085884; cv=none; d=google.com; s=arc-20160816; b=fi84O7YNUk5VoY80yR7SiYBTieJZWHXyiASaLYsBAg7Q9gpFgcDMSTJeBeNiobKpL1 G4a3hhtDEra4aCtr5K7vZtd3P4r6nGHu7SBH5fqiB0ma/v+jxh9bGsMLuI0jcg536Poc mt9BI718Aq2zeUOCCbTlBG5GKN/9XjFCBY6x172Icouehrurx1fy4RjSsyZVBi95MS8P 125LVCNnfhKjL2Wx9RoGsADMOjcMQl3A4W8F7i1cuY3cOq7FBF04DjCMEdeJ+uFqvN3/ DjbIg76Yk3XY78OlbCqPOGYwHWofCUPKQRGVcWIvHQodUw6BrLOmrETDi+BiIzl3qPMW C+Yg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature:dkim-filter; bh=urjxFy2NEO4IWkWWBxKr5z0yKlOgm41OIQHm50hlY30=; b=lXtUvB3EGfckz1G0p8csC9mSAdMNxLnitA+5kuBCO8AB8S9AdPHloqee5JAO+ro+be hDHy285YuxPFA6hMW7T0nXOtlGgO8aijQVzp1rvChpuiqILP6hxMlgkRp//SZYWC7dGD 2WP7tC/c4Jr13Kr2L7pAQ0BNrrHyN8HoFmCoNAFxCkfjjNk6IfG5ccxwZNTvmX1oBZuY D8Plx30ToMWFJT/Bq1Y745vl6biNzChlTCfKZxNbi60VpsU7Xr1DFbS2+NEliSByd03k Vg5eE8DjbSpG41S7jaERXtxaurO/NGhLgbvj4oGaue6T9YKeXu8JHzy0/i1/2fPK6h/2 Fk9w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=bml5OGrd; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r5si7129643pgp.88.2019.06.09.06.11.06; Sun, 09 Jun 2019 06:11:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=bml5OGrd; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728591AbfFINJP (ORCPT + 99 others); Sun, 9 Jun 2019 09:09:15 -0400 Received: from conssluserg-02.nifty.com ([210.131.2.81]:31087 "EHLO conssluserg-02.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728468AbfFINJP (ORCPT ); Sun, 9 Jun 2019 09:09:15 -0400 Received: from mail-vs1-f46.google.com (mail-vs1-f46.google.com [209.85.217.46]) (authenticated) by conssluserg-02.nifty.com with ESMTP id x59D9AP2031817; Sun, 9 Jun 2019 22:09:11 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com x59D9AP2031817 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1560085751; bh=urjxFy2NEO4IWkWWBxKr5z0yKlOgm41OIQHm50hlY30=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=bml5OGrd3jqBJvFoAisXFI7WMZzzdQbhDh0PKg2+B73PLIhW7o9K/4eAuaMhYRQF+ QAKakDzS+W3mMarIxYuRoI4o4B9TK3eoG33Dk+X0b/z8KitpqjeQgd0Mh4PK1NWLL5 ppHBKT6kZXjYOByep1HeUpTmeFjw+qGKhMDPkMmGZRMUW1Rt/SCeVaiVcTPV6mHtAh sk1lO51mRIj38G0mOQqM3j6u1WL9NhJ3/zJpjG4DnyDTrb0BysjM4hHablUNQqFQSy mj5T6CUn7L3gR+5FZIXuDzOahtbmjMDhDAIrkZxto/P4FRwe9LaEj3vmY0WB0g9PCq Z18qEuTyi1u5w== X-Nifty-SrcIP: [209.85.217.46] Received: by mail-vs1-f46.google.com with SMTP id v6so3806647vsq.4; Sun, 09 Jun 2019 06:09:10 -0700 (PDT) X-Gm-Message-State: APjAAAX0wtlc4TdJnACaEAt4vZKEjvGICQAi6LlgAfSHUbZc9VfUzdjG 2BY1Znk/Ud5WBwXa54m/HjORuetFDln0u0iNhF0= X-Received: by 2002:a67:7fcc:: with SMTP id a195mr13075826vsd.181.1560085749841; Sun, 09 Jun 2019 06:09:09 -0700 (PDT) MIME-Version: 1.0 References: <20190604111334.22182-1-yamada.masahiro@socionext.com> <8cf48e20064eabdfe150795365e6ca6f36032e9f.camel@perches.com> <20190604134213.GA26263@kroah.com> <20190605051040.GA22760@kroah.com> <20190605071413.779bd821@coco.lan> In-Reply-To: From: Masahiro Yamada Date: Sun, 9 Jun 2019 22:08:33 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] media: do not use C++ style comments in uapi headers To: Joe Perches Cc: Julia Lawall , Mauro Carvalho Chehab , Greg KH , Arnd Bergmann , Linux Media Mailing List , Thomas Gleixner , Randy Dunlap , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jun 9, 2019 at 8:57 PM Joe Perches wrote: > > On Sun, 2019-06-09 at 16:14 +0900, Masahiro Yamada wrote: > > Hi Joe, > > > > On Thu, Jun 6, 2019 at 2:06 AM Joe Perches wrote: > > > Perhaps a checkpatch change too: > > > > > > The first block updates unsigned only bitfields > > > The second tests uapi definitions and suggests "__ > > > Good. > > > > In addition, > > > > "warn if __u8, __u16, __u32, __u64 are used outside of uapi/" > > > > Lots of kernel-space headers use __u{8,16,32,64} instead of u{8,16,32,64} > > just because developers often miss to understand when to use > > the underscore-prefixed types. > > The problem there is that checkpatch can't know if the > __ being used is for an actual uapi use or not. > > coccinelle could be much better at that. Why? u{8,16,32,64} are _exactly_ the same as __u{8,16,32,64}. See include/asm-generic/int-ll64.h We just use __u{8,16,32,64} for user-space to avoid identifier name conflict, but we do not have reason to do so for kernel-space. -- Best Regards Masahiro Yamada