From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>,
"David S. Miller" <davem@davemloft.net>
Cc: Eric Dumazet <edumazet@google.com>,
Mel Gorman <mgorman@techsingularity.net>,
Willem de Bruijn <willemb@google.com>,
Florian Westphal <fw@strlen.de>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] net/skbuff: don't waste memory reserves
Date: Fri, 19 Apr 2019 06:36:58 -0700 [thread overview]
Message-ID: <299e5bb3-665b-2d3c-fa4c-75466c4a51bf@gmail.com> (raw)
In-Reply-To: <c2c270d9-29c0-b993-84c5-4c994608f7c8@virtuozzo.com>
On 04/19/2019 06:17 AM, Andrey Ryabinin wrote:
>
>
> On 4/18/19 9:55 PM, Eric Dumazet wrote:
>> Are you targeting net or net-next tree ?
>>
>
> I think it's up to Dave to decide where the patches should go. They apply cleanly on both trees.
> The last two patches just minor cleanups so they are definitely net-next material.
>
Not at all, please carefully read
Documentation/networking/netdev-FAQ.rst
Q: How do I indicate which tree (net vs. net-next) my patch should be in?
You need to split your patches in two series, not assume that David will manually do
the manual work for you.
Thank you
next prev parent reply other threads:[~2019-04-19 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 18:05 [PATCH 1/4] net/skbuff: don't waste memory reserves Andrey Ryabinin
2019-04-18 18:05 ` [PATCH 2/4] net/skbuff: warn if kmalloc_reserve() fails to allocate memory Andrey Ryabinin
2019-04-18 18:05 ` [PATCH 3/4] net/skbuff: remove unused skb_propagate_pfmemalloc() Andrey Ryabinin
2019-04-18 18:05 ` [PATCH 4/4] net/skbuff: kmalloc_reserve(): remove unused argument Andrey Ryabinin
2019-04-18 18:55 ` [PATCH 1/4] net/skbuff: don't waste memory reserves Eric Dumazet
2019-04-18 18:56 ` David Miller
2019-04-19 13:17 ` Andrey Ryabinin
2019-04-19 13:36 ` Eric Dumazet [this message]
2019-04-19 13:41 ` Eric Dumazet
2019-04-19 16:25 ` Andrey Ryabinin
2019-04-19 16:27 ` Eric Dumazet
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=299e5bb3-665b-2d3c-fa4c-75466c4a51bf@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=aryabinin@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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).