From: Max Krasnyansky <maxk@qualcomm.com>
To: "Jon Maloy (QB/EMC)" <jon.maloy@ericsson.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
allan.stephens@windriver.com
Subject: Re: [TIPC] Missing null check in the socket code.
Date: Wed, 21 Feb 2007 13:22:04 -0800 [thread overview]
Message-ID: <45DCB7FC.8000100@qualcomm.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAADCB6A2@ecamlmw720.eamcs.ericsson.se>
Hi Jon,
> Acknowledged. We'll deliver it along with
> some other patches ASAP.
Thanx
Did you get a chance to look at my other patch for the header packing ?
Max
next prev parent reply other threads:[~2007-02-21 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 6:27 [TIPC] Properly mask header fields Max Krasnyansky
2007-02-16 6:27 ` [TIPC] Missing null check in the socket code Max Krasnyansky
2007-02-20 18:48 ` Max Krasnyansky
2007-02-21 14:02 ` Jon Maloy (QB/EMC)
2007-02-21 21:22 ` Max Krasnyansky [this message]
2007-02-20 18:47 ` [TIPC] Properly mask header fields Max Krasnyansky
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=45DCB7FC.8000100@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=allan.stephens@windriver.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.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).