From: kuznet@ms2.inr.ac.ru
To: ak@suse.DE (Andi Kleen)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Networking: RFC1122 and 1123 status for kernel 2.4
Date: Fri, 8 Dec 2000 19:41:22 +0300 (MSK) [thread overview]
Message-ID: <200012081641.TAA16371@ms2.inr.ac.ru> (raw)
In-Reply-To: <20001208165855.A20706@gruyere.muc.suse.de> from "Andi Kleen" at Dec 8, 0 07:15:00 pm
Hello!
> Kill it ;)
Great day! Nobody will cry that information sort of this:
* MUST NOT send ICMP errors in reply to:
* ICMP errors (OK)
* Broadcast/multicast datagrams (OK)
* MAC broadcasts (OK)
* Non-initial fragments (OK)
* Datagram with a source address that isn't a single host. (OK)
is not available, I hope. 8)
BTW what is this? It is just a question, I missed even the moment, when these
things appeared:
/**
* kfree_skb - free an sk_buff
* @skb: buffer to free
*
* Drop a reference to the buffer and free it if the usage count has
* hit zero.
*/
People, who need _literal_ translation from C to English to understand
two lines of code, really exist in the nature? To be honest, I would not ever
understand what is to "drop a reference to the buffer and free it
if the usage count has hit zero" not looking to code. 8)
Seven times:
* If this function is called from an interrupt gfp_mask() must be
* %GFP_ATOMIC.
Deep thought, of course. Deep enough to be repeated in each place,
where gfp is used. 8)
Well, I am a fossil, of course, and like to read sources printed on paper
and all these pretentions to convert readbale text to hypertext irritate me.
But such deep thoughts eat even more expensive space on screen!
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 15:31 Andi Kleen
2000-12-08 14:46 ` Fabien Ribes
2000-12-08 14:54 ` David S. Miller
2000-12-08 15:28 ` David S. Miller
2000-12-08 15:58 ` Andi Kleen
2000-12-08 16:41 ` kuznet [this message]
2000-12-08 16:48 ` Andi Kleen
2000-12-08 17:14 ` Alan Cox
2000-12-08 17:13 ` Alan Cox
2000-12-08 19:06 ` kuznet
2000-12-08 19:34 ` Christoph Hellwig
2000-12-08 23:17 ` Christoph Hellwig
2000-12-09 0:00 ` Alan Cox
2000-12-11 22:06 ` David S. Miller
2000-12-13 17:01 ` David S. Miller
2000-12-13 17:14 ` Fabien Ribes
2000-12-08 16:19 ` Fabien Ribes
2000-12-08 16:37 ` Andi Kleen
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=200012081641.TAA16371@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=ak@suse.DE \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®