linux-kernel - Re: [v5 00/14] Add support for Bosch BNO055 IMU

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]

Message-ID: <CAHp75VeRV-Nv_zw6Qe9huXzqi14GJhWxQEpbbejn0z33zPYKtg@mail.gmail.com>
Date:   Mon, 2 May 2022 10:52:59 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Andrea Merello <andrea.merello@...il.com>
Cc:     Jonathan Cameron <jic23@...nel.org>,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        linux-iio <linux-iio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        devicetree <devicetree@...r.kernel.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>,
        Andrea Merello <andrea.merello@....it>
Subject: Re: [v5 00/14] Add support for Bosch BNO055 IMU

On Mon, May 2, 2022 at 10:31 AM Andrea Merello <andrea.merello@...il.com> wrote:
> Il giorno lun 2 mag 2022 alle ore 09:48 Andy Shevchenko
> <andy.shevchenko@...il.com> ha scritto:

...

> > > BTW I have also gone through some kernel-robot reports; they also
> > > state "If you fix the issue, kindly add following tag as appropriate
> > > Reported-by: kernel test robot <lkp@...el.com>". I'd say that it would
> > > be OK to add this tag to a patch that just fixes what is reported, but
> > > I'm unsure whether it is appropriate to add this tag to the patches in
> > > my series, because they add the code and the fix at once. Any advice
> > > here?
> >
> > For this we specifically amended the kernel documentation recently.
> > https://www.kernel.org/doc/html/latest/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
> >
> > "The tag is intended for bugs; please do not use it to credit feature requests."
>
> Well, no any feature request to credit here; a bug and its fix are
> involved. Sounds more like a "yes" so far.. But it wouldn't be clear
> what the robot did report indeed (squashed bugs and fixes).. Maybe a
> "thank" in the cover letter also to it would suffice?

The reported from bots should be used when your patches.changes
induced by those reports, it seems otherwise in your case.,


-- 
With Best Regards,
Andy Shevchenko