All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Simon Horman <simon.horman@netronome.com>
Cc: John Fastabend <john.r.fastabend@intel.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: flow: Guard against accessing non-existent attributes
Date: Mon, 29 Dec 2014 09:53:30 -0800	[thread overview]
Message-ID: <54A1951A.2070209@gmail.com> (raw)
In-Reply-To: <1419819455-19109-1-git-send-email-simon.horman@netronome.com>

On 12/28/2014 06:17 PM, Simon Horman wrote:
> Signed-off-by: Simon Horman <simon.horman@netronome.com>
> ---
>   net/core/flow_table.c | 11 +++++++++++
>   1 file changed, 11 insertions(+)

Great thanks. I rolled it into the patches I should hopefully have
ready to submit later today.

By the way I got this working on rocker now so we can test it easier,
I'll post the driver updates as well.

.John

-- 
John Fastabend         Intel Corporation

  reply	other threads:[~2014-12-29 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  2:17 [PATCH] net: flow: Guard against accessing non-existent attributes Simon Horman
2014-12-29 17:53 ` John Fastabend [this message]
2015-01-05  2:04   ` Simon Horman

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=54A1951A.2070209@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=john.r.fastabend@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.horman@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.