From: David Miller <davem@davemloft.net>
To: pravin.shedge4linux@gmail.com
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
fw@strlen.de, andrew@lunn.ch, mingo@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 27/45] net: remove duplicate includes
Date: Sun, 10 Dec 2017 23:04:32 -0500 (EST) [thread overview]
Message-ID: <20171210.230432.1241639159245478272.davem@davemloft.net> (raw)
In-Reply-To: <CALSsfODmhEai9JhF_DmOMGnnf6CtjNohoJxWhFxwxddTE0yXkw@mail.gmail.com>
From: Pravin Shedge <pravin.shedge4linux@gmail.com>
Date: Sun, 10 Dec 2017 23:30:21 +0530
> On Thu, Dec 7, 2017 at 2:28 AM, David Miller <davem@davemloft.net> wrote:
>> From: Pravin Shedge <pravin.shedge4linux@gmail.com>
>> Date: Wed, 6 Dec 2017 23:02:58 +0530
>>
>>> These duplicate includes have been found with scripts/checkincludes.pl but
>>> they have been removed manually to avoid removing false positives.
>>>
>>> Signed-off-by: Pravin Shedge <pravin.shedge4linux@gmail.com>
>>
>> Networking patches need to be sent to netdev@vger.kernel.org
>>
>> Thank you.
>
> -- Adding netdev@vger.kernel.org for reviewing networking patches.
Doesn't work like that.
You have to post the actual patch freshly to the netdev mailing list
so that it gets properly queued in patchwork and can be reviewed.
You can't just add netdev to the CC: in a reply to my email, that
doesn't do any good at all.
next prev parent reply other threads:[~2017-12-11 4:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 17:32 [PATCH 27/45] net: remove duplicate includes Pravin Shedge
2017-12-06 20:58 ` David Miller
2017-12-10 18:00 ` Pravin Shedge
2017-12-11 4:04 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-11 16:39 Pravin Shedge
2017-12-11 19:04 ` Pablo Neira Ayuso
2017-12-13 18:19 ` 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=20171210.230432.1241639159245478272.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pravin.shedge4linux@gmail.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).