[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5bc4f8ce9a6c40029043bc902a38af25@intel.com>
Date: Fri, 13 Nov 2020 00:32:55 +0000
From: "Li, Philip" <philip.li@...el.com>
To: Jakub Kicinski <kuba@...nel.org>, lkp <lkp@...el.com>
CC: Dmytro Shytyi <dmytro@...tyi.net>, kuznet <kuznet@....inr.ac.ru>,
yoshfuji <yoshfuji@...ux-ipv6.org>,
liuhangbin <liuhangbin@...il.com>, davem <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"kbuild-all@...ts.01.org" <kbuild-all@...ts.01.org>
Subject: RE: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC with
prefixes of arbitrary length in PIO
> 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@...el.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@...el.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@...ts.01.org
> To unsubscribe send an email to kbuild-all-leave@...ts.01.org
Powered by blists - more mailing lists