public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: davem@davemloft.net, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BK] TUN/TAP driver update and fixes for 2.6.BK
Date: Wed, 12 Jan 2005 18:19:19 -0500	[thread overview]
Message-ID: <41E5B077.8030300@pobox.com> (raw)
In-Reply-To: <41E5A5DA.1010301@qualcomm.com>

Max Krasnyansky wrote:
> Dave, Andrew,
> 
> Could one of you please pull TUN/TAP driver updates from my tree
>         bk://maxk.bkbits.net/tun-2.6
> 
> This will update the following files:
> 
>  drivers/net/Kconfig    |    1
>  drivers/net/tun.c      |  145 
> ++++++++++++++++++++++++++++++++++++++++++-------
>  include/linux/if_tun.h |    2
>  3 files changed, 128 insertions(+), 20 deletions(-)


Non-technical comments:

1) Please send drivers/net patches to me and netdev@oss.sgi.com

2) Consider using the bk-make-sum script (in Documentation/BK-usage/) to 
generate your summary.  This will add a "bk pull " prefix to your BK url 
particularly, making it even easier to cut-n-paste.

3) Please include a patch in your submission so that list readers may 
review your changes, not just the BK users.


Technical comments:

1) Accepted, I pulled it into my netdev-2.6 queue

2) in your implementation of tun_get_drvinfo(), it may be nice to 
include the tun/tap interface number in info->bus_info, to differentiate 
between multiple tun interfaces or multiple tap interfaces.

3) You might consider moving tun_set_msglevel() completely inside 
TUN_DEBUG ifdef.

4) use of MODULE_VERSION() is recommended



  parent reply	other threads:[~2005-01-12 23:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 22:34 [BK] TUN/TAP driver update and fixes for 2.6.BK Max Krasnyansky
2005-01-12 23:01 ` Andrew Morton
2005-01-12 23:14   ` Jeff Garzik
2005-01-12 23:16   ` Max Krasnyansky
2005-01-12 23:26     ` Andrew Morton
2005-01-12 23:40       ` Max Krasnyansky
2005-01-12 23:19 ` Jeff Garzik [this message]
2005-01-12 23:50   ` Max Krasnyansky
2005-01-12 23:54     ` Jeff Garzik

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=41E5B077.8030300@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.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