linux-kernel - Re: [PATCH v2] Documentation: bno055: separate SPDX identifier and page title

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 4 Jul 2022 21:49:58 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Linux Documentation List <linux-doc@...r.kernel.org>,
        kernel test robot <lkp@...el.com>,
        Jonathan Corbet <corbet@....net>,
        Andrea Merello <andrea.merello@....it>,
        Jonathan Cameron <jic23@...nel.org>,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Matt Ranostay <matt.ranostay@...sulko.com>,
        Alexandru Ardelean <ardeleanalex@...il.com>,
        jmondi <jacopo@...ndi.org>,
        linux-iio <linux-iio@...r.kernel.org>,
        devicetree <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] Documentation: bno055: separate SPDX identifier and
 page title

On Mon, Jul 4, 2022 at 5:41 AM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> kernel test robot reported htmldocs warning:
>
> Documentation/iio/bno055.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
>
> The warning above is caused by missing blank line separator between SPDX
> identifier and page title.
>
> Add the blank line to fix the warning.
>
> Link: https://lore.kernel.org/lkml/202207031509.DlBrHyaw-lkp@intel.com/
> Fixes: ec0c70cb45507d ("docs: iio: add documentation for BNO055 driver")
> Reported-by: kernel test robot <lkp@...el.com>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@...il.com>

> Cc: Jonathan Corbet <corbet@....net>
> Cc: Andrea Merello <andrea.merello@....it>
> Cc: Jonathan Cameron <jic23@...nel.org>
> Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> Cc: Lars-Peter Clausen <lars@...afoo.de>
> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Matt Ranostay <matt.ranostay@...sulko.com>
> Cc: Alexandru Ardelean <ardeleanalex@...il.com>
> Cc: jacopo@...ndi.org
> Cc: linux-iio@...r.kernel.org
> Cc: devicetree@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org (open list)

It's a very noisy Cc list which will go in the git history. Instead,
use --to and --cc parameters of `git format-patch`. Maintainers
usually use `b4` tool that adds a Link tag to the patch itself on the
Lore archive which will keep track on the Cc list anyway.

-- 
With Best Regards,
Andy Shevchenko