From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.5.69] IPV4/6 inetsw using RCU
Date: Fri, 9 May 2003 07:49:12 +0200 [thread overview]
Message-ID: <20030509054912.GL15829@Wotan.suse.de> (raw)
In-Reply-To: <20030508.154320.128592193.davem@redhat.com>
On Thu, May 08, 2003 at 03:43:20PM -0700, David S. Miller wrote:
> From: Stephen Hemminger <shemminger@osdl.org>
> Date: Thu, 8 May 2003 15:33:07 -0700
>
> This is a revised version of the earlier brlock removal patch, and
> addresses all comments received so far. It is stable and works
> reliably, but Dave, you may want to wait for any additional
> comments before applying.
>
> Okie dokie. The patch looks fine to me. Just let me know when
> it's ready to go in.
FWIW it looks good to me too.
-Andi
prev parent reply other threads:[~2003-05-09 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 22:33 [PATCH 2.5.69] IPV4/6 inetsw using RCU Stephen Hemminger
2003-05-08 22:43 ` David S. Miller
2003-05-09 5:49 ` Andi Kleen [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=20030509054912.GL15829@Wotan.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).