From: David Miller <davem@davemloft.net>
To: dan.carpenter@oracle.com
Cc: Yuval.Mintz@cavium.com, Chopra@mwanda, Manish.Chopra@cavium.com,
Ariel.Elior@cavium.com, everest-linux-l2@cavium.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] qede: allocate enough data for ->arfs_fltr_bmap
Date: Thu, 20 Apr 2017 16:25:47 -0400 (EDT) [thread overview]
Message-ID: <20170420.162547.1676158647736779786.davem@davemloft.net> (raw)
In-Reply-To: <20170419095432.GA4266@mwanda>
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Wed, 19 Apr 2017 12:54:33 +0300
> We've got the number of longs, yes, but we should multiply by
> sizeof(long) to get the number of bytes needed.
>
> Fixes: e4917d46a653 ("qede: Add aRFS support")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks.
prev parent reply other threads:[~2017-04-20 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 9:54 [PATCH net-next] qede: allocate enough data for ->arfs_fltr_bmap Dan Carpenter
2017-04-19 10:12 ` Mintz, Yuval
2017-04-20 20:25 ` 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=20170420.162547.1676158647736779786.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ariel.Elior@cavium.com \
--cc=Chopra@mwanda \
--cc=Manish.Chopra@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=dan.carpenter@oracle.com \
--cc=everest-linux-l2@cavium.com \
--cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).