From: David Miller <davem@davemloft.net>
To: xiaosuo@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/8]: net: rps: reset network header before calling skb_get_rxhash()
Date: Thu, 19 Aug 2010 17:08:51 -0700 (PDT) [thread overview]
Message-ID: <20100819.170851.258130071.davem@davemloft.net> (raw)
In-Reply-To: <1282107656-3386-1-git-send-email-xiaosuo@gmail.com>
From: Changli Gao <xiaosuo@gmail.com>
Date: Wed, 18 Aug 2010 13:00:56 +0800
> skb_get_rxhash() assumes the network header pointer of the skb is set
> properly after the commit:
>
> commit bfb564e7391340638afe4ad67744a8f3858e7566
> Author: Krishna Kumar <krkumar2@in.ibm.com>
> Date: Wed Aug 4 06:15:52 2010 +0000
>
> core: Factor out flow calculation from get_rps_cpu
>
> Signed-off-by: Changli Gao <xiaosuo@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2010-08-20 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 5:00 [PATCH 1/8]: net: rps: reset network header before calling skb_get_rxhash() Changli Gao
2010-08-20 0:08 ` 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=20100819.170851.258130071.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xiaosuo@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).