From: Meelis Roos <mroos@linux.ee>
To: netdev@vger.kernel.org
Subject: ipv4_get_l4proto: Frag of proto 17
Date: Tue, 21 Aug 2007 13:56:36 +0300 (EEST) [thread overview]
Message-ID: <Pine.SOC.4.64.0708211355310.24028@math.ut.ee> (raw)
Yesterdays git snapsot on a normal home PC spams dmesg with the
following line:
ipv4_get_l4proto: Frag of proto 17
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2007-08-21 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 10:56 Meelis Roos [this message]
2007-08-30 7:08 ` ipv4_get_l4proto: Frag of proto 17 Patrick McHardy
2007-08-30 13:04 ` Meelis Roos
2007-09-01 5:28 ` Patrick McHardy
2007-09-01 15:04 ` Meelis Roos
2007-09-01 16:19 ` Patrick McHardy
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=Pine.SOC.4.64.0708211355310.24028@math.ut.ee \
--to=mroos@linux.ee \
--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).