[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <710ae0adfbc343aa81403055c31665c6@meizu.com>
Date: Wed, 23 Mar 2022 06:30:56 +0000
From: 白浩文 <baihaowen@...zu.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 答复: [PATCH] net: l2tp: Fix duplicate included trace.h
thx for pointing out my mistaken.
________________________________________
发件人: Jakub Kicinski <kuba@...nel.org>
发送时间: 2022年3月23日 13:14:18
收件人: 白浩文
抄送: davem@...emloft.net; pabeni@...hat.com; netdev@...r.kernel.org; linux-kernel@...r.kernel.org
主题: Re: [PATCH] net: l2tp: Fix duplicate included trace.h
On Wed, 23 Mar 2022 11:38:25 +0800 Haowen Bai wrote:
> Clean up the following includecheck warning:
>
> net/l2tp/l2tp_core.c: trace.h is included more than once.
>
> No functional change.
This one doesn't build either.
You must validate your patches to the best of your ability.
If the best of your ability does not include firing up
a compiler - that will be a problem.
Powered by blists - more mailing lists