From: Yuehaibing <yuehaibing@huawei.com>
To: Edward Cree <ecree@solarflare.com>,
"David S . Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: <netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH net-next] sfc: remove duplicated include from ef10.c
Date: Sat, 11 Jan 2020 09:56:52 +0800 [thread overview]
Message-ID: <db6af9a7-3229-edf0-d650-af4287e32661@huawei.com> (raw)
In-Reply-To: <422eff3d-05ea-d967-ff1b-448b6dc9dcb5@solarflare.com>
On 2020/1/10 19:57, Edward Cree wrote:
> On 10/01/2020 01:35, YueHaibing wrote:
>> Remove duplicated include.
>>
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> Acked-by: Edward Cree <ecree@solarflare.com>
> but you seem to have come up with a strange CC list, full of bpf maintainers
> rather than sfc driver maintainers; check your submission scripts? (AFAIK
> the MAINTAINERS file has the right things in.)
Thanks, I will check this.
>
> -Ed
>> ---
>> drivers/net/ethernet/sfc/ef10.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/sfc/ef10.c b/drivers/net/ethernet/sfc/ef10.c
>> index dc037dd927f8..fa460831af7d 100644
>> --- a/drivers/net/ethernet/sfc/ef10.c
>> +++ b/drivers/net/ethernet/sfc/ef10.c
>> @@ -16,7 +16,6 @@
>> #include "workarounds.h"
>> #include "selftest.h"
>> #include "ef10_sriov.h"
>> -#include "rx_common.h"
>> #include <linux/in.h>
>> #include <linux/jhash.h>
>> #include <linux/wait.h>
>>
>>
>>
>
>
> .
>
next prev parent reply other threads:[~2020-01-11 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 1:35 YueHaibing
2020-01-10 11:57 ` Edward Cree
2020-01-11 1:56 ` Yuehaibing [this message]
2020-01-11 7:11 ` David Miller
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=db6af9a7-3229-edf0-d650-af4287e32661@huawei.com \
--to=yuehaibing@huawei.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=jakub.kicinski@netronome.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®