[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27ed1d631d1c804565056c4ff207dc66cfa78c80.camel@microchip.com>
Date: Wed, 7 Dec 2022 04:15:04 +0000
From: <Arun.Ramadoss@...rochip.com>
To: <richardcochran@...il.com>
CC: <andrew@...n.ch>, <linux-kernel@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>, <vivien.didelot@...il.com>,
<olteanv@...il.com>, <linux@...linux.org.uk>, <ceggers@...i.de>,
<Tristram.Ha@...rochip.com>, <f.fainelli@...il.com>,
<kuba@...nel.org>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<netdev@...r.kernel.org>, <Woojung.Huh@...rochip.com>,
<davem@...emloft.net>
Subject: Re: [Patch net-next v2 06/13] net: ptp: add helper for one-step P2P
clocks
Hi Richard,
On Tue, 2022-12-06 at 08:38 -0800, Richard Cochran wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Tue, Dec 06, 2022 at 02:44:21PM +0530, Arun Ramadoss wrote:
> > From: Christian Eggers <ceggers@...i.de>
> >
> >
> > Reported-by: kernel test robot <lkp@...el.com>
>
> How can a test robot report new code additions?
Test robot ran the compilation test for the patch v1 and found
compilation error when CONFIG_NET_PTP_CLASSIFY is not enabled. It is
due to mismatch in function name defined in with and without
PTP_CLASSIFY enabled.
https://lore.kernel.org/netdev/202211290847.wW6xCbMT-lkp@intel.com/
In the message, it is mentioned like
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@...el.com>
I initially thought reported-by tag needs to added only for the bug fix
patch. I was in confusion where to add the tag whether in commit
description or in the patch revision message.
Kindly suggest on where to add tag, before signed-off or in the patch
revision list.
Thanks
Arun
>
> Thanks,
> Richard
Powered by blists - more mailing lists