[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b1461c5-2398-b15d-f704-543bc7771eb7@intel.com>
Date: Thu, 12 Nov 2020 18:01:28 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: kernel test robot <lkp@...el.com>,
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
Subject: Re: [PATCH net-next] net: Variable SLAAC: SLAAC with prefixes of
arbitrary length in PIO
On 11/12/20 5:53 PM, Jakub Kicinski wrote:
>> I do agree, though, that it's confusing *what* they reported, especially
>> if the patch in question is fixing something *else*. Rather than invent
>> a new tag, maybe a comment would suffice:
>>
>> Reported-by: kernel test robot <lkp@...el.com> # bug in earlier revision
> Fine by me, although its not common to add Reported-by tags for people
> who point out issues in review, so why add a tag for the bot?
If for no other reason, it helps Philip and team generate accurate data
on how effective and helpful the bot is. That, in turn, plays a role in
making sure that Intel keeps funding it.
Powered by blists - more mailing lists