From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Joe Perches <joe@perches.com>
Cc: Christoph Lameter <clameter@sgi.com>,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
coreteam@netfilter.org
Subject: Re: [PATCH] mm/slab.c - use angle brackets for include
Date: Wed, 05 Mar 2008 23:20:40 +0200 [thread overview]
Message-ID: <47CF0EA8.5000104@cs.helsinki.fi> (raw)
In-Reply-To: <1204751900.17370.72.camel@localhost>
Joe Perches wrote:
> Seems a likely idea, but maybe netfilter shouldn't bother
> with a minimum?
Agreed and sent a patch to do just that.
prev parent reply other threads:[~2008-03-05 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1204678035.5180.94.camel@localhost>
[not found] ` <47CEEFF4.7080605@cs.helsinki.fi>
[not found] ` <Pine.LNX.4.64.0803051206160.30357@schroedinger.engr.sgi.com>
[not found] ` <1204748782.17370.47.camel@localhost>
[not found] ` <Pine.LNX.4.64.0803051250440.30634@schroedinger.engr.sgi.com>
2008-03-05 21:18 ` [PATCH] mm/slab.c - use angle brackets for include Joe Perches
2008-03-05 21:20 ` Pekka Enberg [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=47CF0EA8.5000104@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=clameter@sgi.com \
--cc=coreteam@netfilter.org \
--cc=joe@perches.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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