From: David Miller <davem@davemloft.net>
To: chucks.8090@gmail.com
Cc: pablo@netfilter.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Net: netfilter: Moved vmalloc call to kmalloc call
Date: Fri, 03 Nov 2017 09:59:47 +0900 (KST) [thread overview]
Message-ID: <20171103.095947.1853556344772237136.davem@davemloft.net> (raw)
In-Reply-To: <20171102231727.12610-1-chucks.8090@gmail.com>
From: Charlie Sale <chucks.8090@gmail.com>
Date: Thu, 2 Nov 2017 19:17:27 -0400
> Fixed FIXME comment in code my changing a vmalloc call
> to a kmalloc call. Thought it would be a good place to
> start for a first patch.
>
> Signed-off-by: Charlie Sale <chucks.8090@gmail.com>
Since this code you are posting doesn't even compile, we have to
assume you didn't functionally test it either.
prev parent reply other threads:[~2017-11-03 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 23:17 [PATCH] Net: netfilter: Moved vmalloc call to kmalloc call Charlie Sale
2017-11-02 23:35 ` Florian Westphal
2017-11-03 0:59 ` 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=20171103.095947.1853556344772237136.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chucks.8090@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).