From: "David S. Miller" <davem@redhat.com>
To: Mitchell Blank Jr <mitch@sfgoth.com>
Cc: chas@cmf.nrl.navy.mil, levon@movementarian.org, netdev@oss.sgi.com
Subject: Re: [PATCH][ATM]: [ioctl][1/8] move vcc_ioctl() to ioctl.c (from levon@movementarian.org)
Date: Thu, 25 Sep 2003 20:55:30 -0700 [thread overview]
Message-ID: <20030925205530.2a166ccc.davem@redhat.com> (raw)
In-Reply-To: <20030925194103.GE31418@gaz.sfgoth.com>
What I'm going to do is just merge in all of what Chas posted
today, you can send me new patches to update this to John's
latest code.
Thanks.
next prev parent reply other threads:[~2003-09-26 3:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030925170342.GA74937@compsoc.man.ac.uk>
2003-09-25 19:28 ` [PATCH][ATM]: [ioctl][1/8] move vcc_ioctl() to ioctl.c (from levon@movementarian.org) chas williams
2003-09-25 19:41 ` Mitchell Blank Jr
2003-09-26 3:55 ` David S. Miller [this message]
2003-09-26 13:48 ` chas williams
2003-09-26 14:05 ` David S. Miller
[not found] <20030925161740.GA71011@compsoc.man.ac.uk>
2003-09-25 16:45 ` chas williams
2003-09-25 16:09 chas williams
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=20030925205530.2a166ccc.davem@redhat.com \
--to=davem@redhat.com \
--cc=chas@cmf.nrl.navy.mil \
--cc=levon@movementarian.org \
--cc=mitch@sfgoth.com \
--cc=netdev@oss.sgi.com \
/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).