From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@colin2.muc.de>
Cc: yoshfuji@linux-ipv6.org, ak@muc.de, netdev@oss.sgi.com
Subject: Re: [PATCH] Make XFRM optional
Date: Mon, 4 Aug 2003 16:51:37 -0700 [thread overview]
Message-ID: <20030804165137.40d744c5.davem@redhat.com> (raw)
In-Reply-To: <20030804203524.GA15874@colin2.muc.de>
On 4 Aug 2003 22:35:24 +0200
Andi Kleen <ak@colin2.muc.de> wrote:
> Ok, here is a new patch again current BKCVS. It also moves the inet_peer_idlock
> only inside netsyms.
This one is missing net/xfrm/xfrm_export.c :-(
Andi, please be more careful with your patches. I'd suggest use
subversions or whatever source management system you like best to help
avoid these problems in the future. You seem to be chronicly making
mistakes like this, as if you're rushing things.
next prev parent reply other threads:[~2003-08-04 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 12:50 [PATCH] Make XFRM optional Andi Kleen
2003-08-04 12:58 ` YOSHIFUJI Hideaki / 吉藤英明
2003-08-04 13:04 ` Andi Kleen
2003-08-04 18:45 ` David S. Miller
2003-08-04 20:35 ` Andi Kleen
2003-08-04 23:49 ` David S. Miller
2003-08-04 23:51 ` David S. Miller [this message]
[not found] ` <20030805135315.GB63394@colin2.muc.de>
2003-08-06 6:08 ` David S. Miller
2003-08-04 15:50 ` Nivedita Singhvi
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=20030804165137.40d744c5.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).