Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: uUX0y3cqj41IbZ2czIFdTp5Y74yjGp27dVXOTXB2rx8kKC5mDDV4pnslOlvUwJWy4E0/KHuysu
 hhKTTiNcga/A==
IronPort-SDR: O4WV4hjsdA5G7ttgHqJHgEGPfwF0hKx2MMEvPJRpDHTiUzuY7gnXHRvd2+ScNIlhwJIXQV7fXn
 wYsCge5A1tKw==
From:   "Li, Philip" <philip.li@intel.com>
To:     Jakub Kicinski <kuba@kernel.org>, lkp <lkp@intel.com>
CC:     Dmytro Shytyi <dmytro@shytyi.net>, kuznet <kuznet@ms2.inr.ac.ru>,
        yoshfuji <yoshfuji@linux-ipv6.org>,
        liuhangbin <liuhangbin@gmail.com>, davem <davem@davemloft.net>,
        netdev <netdev@vger.kernel.org>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>
Subject: RE: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC with
 prefixes of arbitrary length in PIO
Thread-Topic: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC
 with prefixes of arbitrary length in PIO
Thread-Index: AQHWt8rnymHV+oRFv0+mSedV58/YYKnEsPmAgACHjsA=
Date:   Fri, 13 Nov 2020 00:32:55 +0000
Message-ID: <5bc4f8ce9a6c40029043bc902a38af25@intel.com>
References: <175b3433a4c.aea7c06513321.4158329434310691736@shytyi.net>
        <202011110944.7zNVZmvB-lkp@intel.com>
 <20201112162423.6b4de8d1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
In-Reply-To: <20201112162423.6b4de8d1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-reaction: no-action
dlp-version: 11.5.1.3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Precedence: bulk

> Subject: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC with
> prefixes of arbitrary length in PIO
> 
> On Wed, 11 Nov 2020 09:34:24 +0800 kernel test robot wrote:
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> 
> Good people of kernel test robot, could you please rephrase this to say
> that the tag is only appropriate if someone is sending a fix up/follow
> up patch?
Thanks for the input, based on your suggestion how about

Kindly add below tag as appropriate if you send a fix up/follow up patch
Reported-by: kernel test robot <lkp@intel.com>

Or any wording change suggestion to make it more clear/friendly?

Thanks

> 
> Folks keep adding those tags on the next revisions of the their patches
> which is quite misleading.
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org