From: Stephen Hemminger <shemminger@vyatta.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jeff@garzik.org,
Alexander Duyck <alexander.h.duyck@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: [PATCH] iproute2: 0 out memory for tc_skbedit struct prior to using it.
Date: Thu, 19 Feb 2009 09:00:24 -0800 [thread overview]
Message-ID: <20090219090024.035fdfeb@extreme> (raw)
In-Reply-To: <9929d2390902091702m1a78acf7oa33ab99092c4ca12@mail.gmail.com>
On Mon, 9 Feb 2009 17:02:48 -0800
Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:
> Stephen - what is the status of this?
>
Similar fix just applied
prev parent reply other threads:[~2009-02-19 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 3:20 [PATCH] iproute2: 0 out memory for tc_skbedit struct prior to using it Jeff Kirsher
2009-02-10 1:02 ` Jeff Kirsher
2009-02-19 17:00 ` Stephen Hemminger [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=20090219090024.035fdfeb@extreme \
--to=shemminger@vyatta.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--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).