From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: lucien.xin@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
marcelo.leitner@gmail.com, dave.hansen@linux.intel.com,
rientjes@google.com, eparis@redhat.com, khorenko@virtuozzo.com
Subject: Re: [PATCHv2 net 0/3] net: add support for flex_array_resize in flex_array
Date: Wed, 12 Dec 2018 16:06:09 -0800 (PST) [thread overview]
Message-ID: <20181212.160609.1564345085630799191.davem@davemloft.net> (raw)
In-Reply-To: <20181212120015.GA7637@hmswarspite.think-freely.org>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Wed, 12 Dec 2018 07:00:15 -0500
> I suggest xin respond to messageid
> 20180523011821.12165-6-kent.overstreet@gmail.com> and send a NAK,
> indicating that his patch seems like it will break the build, as,
> looking through it, it never removes flex_array calls from the sctp
> code. If kent reposts with a conversion of the sctp code to radix
> trees, we're done. If not, you can move forward with this commit.
Ok, Xin please do that so we can more forward.
Thanks Neil.
prev parent reply other threads:[~2018-12-13 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 6:30 [PATCHv2 net 0/3] net: add support for flex_array_resize in flex_array Xin Long
2018-12-07 6:30 ` [PATCHv2 net 1/3] flex_array: make FLEX_ARRAY_BASE_SIZE the same value of FLEX_ARRAY_PART_SIZE Xin Long
2018-12-07 6:30 ` [PATCHv2 net 2/3] flex_array: support flex_array_resize Xin Long
2018-12-07 6:30 ` [PATCHv2 net 3/3] sctp: fa_resize sctp stream instead of redo fa_alloc Xin Long
2018-12-07 18:10 ` [PATCHv2 net 0/3] net: add support for flex_array_resize in flex_array Dave Hansen
2018-12-12 6:50 ` David Miller
2018-12-12 12:00 ` Neil Horman
2018-12-13 0:06 ` David Miller [this message]
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=20181212.160609.1564345085630799191.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dave.hansen@linux.intel.com \
--cc=eparis@redhat.com \
--cc=khorenko@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rientjes@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).