From: 白浩文 <baihaowen@meizu.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH] net: l2tp: Fix duplicate included trace.h
Date: Wed, 23 Mar 2022 06:30:56 +0000 [thread overview]
Message-ID: <710ae0adfbc343aa81403055c31665c6@meizu.com> (raw)
In-Reply-To: <20220322221418.55f6a665@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
thx for pointing out my mistaken.
________________________________________
发件人: Jakub Kicinski <kuba@kernel.org>
发送时间: 2022年3月23日 13:14:18
收件人: 白浩文
抄送: davem@davemloft.net; pabeni@redhat.com; netdev@vger.kernel.org; linux-kernel@vger.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.
next prev parent reply other threads:[~2022-03-23 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 3:38 [PATCH] net: l2tp: Fix duplicate included trace.h Haowen Bai
2022-03-23 5:14 ` Jakub Kicinski
2022-03-23 6:30 ` 白浩文 [this message]
2022-03-23 12:58 ` kernel test robot
2022-03-23 13:38 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=710ae0adfbc343aa81403055c31665c6@meizu.com \
--to=baihaowen@meizu.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).