From: "David S. Miller" <davem@redhat.com>
To: acmay@acmay.homeip.net
Cc: linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] ipip.c & ip_gre.c (Add Tunnel return)
Date: Tue, 25 Sep 2001 15:31:19 -0700 (PDT) [thread overview]
Message-ID: <20010925.153119.91756467.davem@redhat.com> (raw)
In-Reply-To: <20010925152628.A8042@ecam.san.rr.com>
In-Reply-To: <20010925152628.A8042@ecam.san.rr.com>
From: andrew may <acmay@acmay.homeip.net>
Date: Tue, 25 Sep 2001 15:26:28 -0700
I think the tunnel drivers should return the name of the
device the tunnel add created. Currently the tunnel_lookup
functions copy the name into the stack var in the ioctl
function but the ioctl copies the parm from the tunnel
device.
Hmmm, net/ipv6/sit.c already has the version you propose. :-)))
Which one is correct?
Alexey, what do you think?
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-09-25 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 22:26 andrew may
2001-09-25 22:31 ` David S. Miller [this message]
2001-09-25 22:36 ` David S. Miller
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=20010925.153119.91756467.davem@redhat.com \
--to=davem@redhat.com \
--cc=acmay@acmay.homeip.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®