From: "David S. Miller" <davem@redhat.com>
To: wa@almesberger.net
Cc: hch@infradead.org, jmorris@intercode.com.au, TSPAT@de.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: crypto API and IBM z990 hardware support
Date: Wed, 09 Jul 2003 18:08:30 -0700 (PDT) [thread overview]
Message-ID: <20030709.180830.39180836.davem@redhat.com> (raw)
In-Reply-To: <20030709220825.A22087@almesberger.net>
From: Werner Almesberger <wa@almesberger.net>
Date: Wed, 9 Jul 2003 22:08:25 -0300
E.g. most of include/net/tcp.h pretty much only matters for
net/ipv4/. It would be so nice if a grep -w thing *.[ch] in
net/ipv4/ would really find all uses of "thing".
Bad example, I'd say that %65 of that file is used in net/ipv6/*.c
files too.
next prev parent reply other threads:[~2003-07-10 1:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 7:07 crypto API and IBM z990 hardware support Thomas Spatzier
2003-07-02 9:35 ` James Morris
2003-07-07 7:09 ` Christoph Hellwig
2003-07-08 2:53 ` David S. Miller
2003-07-08 3:37 ` Roland Dreier
2003-07-08 3:35 ` David S. Miller
2003-07-10 1:08 ` Werner Almesberger
2003-07-10 1:08 ` David S. Miller [this message]
2003-07-10 2:06 ` Werner Almesberger
2003-07-10 2:06 ` David S. Miller
2003-07-10 2:37 ` Werner Almesberger
2003-07-11 0:02 ` David S. Miller
[not found] ` <mailman.1057799700.15422.linux-kernel2news@redhat.com>
2003-07-10 5:55 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 12:35 Thomas Spatzier
2003-07-02 16:57 ` James Morris
2003-07-07 7:11 ` Christoph Hellwig
2003-07-07 10:27 ` James Morris
2003-07-02 20:23 Ulrich Weigand
[not found] <4P45.5YN.11@gated-at.bofh.it>
[not found] ` <4T81.24d.41@gated-at.bofh.it>
2003-07-02 22:06 ` Arnd Bergmann
2003-07-06 14:08 ` James Morris
2003-07-06 17:46 ` Arnd Bergmann
2003-07-07 7:14 ` Christoph Hellwig
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=20030709.180830.39180836.davem@redhat.com \
--to=davem@redhat.com \
--cc=TSPAT@de.ibm.com \
--cc=hch@infradead.org \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wa@almesberger.net \
/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.