netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Daniele Orlandi <daniele@orlandi.com>
Cc: netdev@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Request for an ARPHRD_
Date: Tue, 25 Oct 2005 00:22:23 +0200	[thread overview]
Message-ID: <20051024222222.GA11005@xi.wantstofly.org> (raw)
In-Reply-To: <200510250008.10409.daniele@orlandi.com>

On Tue, Oct 25, 2005 at 12:08:09AM +0200, Daniele Orlandi wrote:

> > First get your code in the kernel, then submit the patch to libpcap.
> 
> Hopefully I will but currently vISDN is not mature enough to be
> evaluated for kernel inclusion.
> 
> I would like to keep it out of the tree while it matures, however I
> would also like to avoid potential constants clashes with outher/future
> code.
> 
> You may see the constants allocation as the first step to include that
> code in the kernel.

Your code might never end up in the kernel at all, for example if you
ever lose interest in it.  The situation that we'd like to avoid is
ending up with reserved constants for code that was never submitted
upstream at all.


cheers,
Lennert

  reply	other threads:[~2005-10-24 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200510240255.28416.daniele@orlandi.com>
     [not found] ` <200510241807.23290.ak@suse.de>
2005-10-24 21:33   ` Request for an ARPHRD_ Daniele Orlandi
2005-10-24 21:51     ` Lennert Buytenhek
2005-10-24 22:08       ` Daniele Orlandi
2005-10-24 22:22         ` Lennert Buytenhek [this message]
2005-10-24 22:58           ` Daniele Orlandi
2005-10-24 22:24     ` Andi Kleen

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=20051024222222.GA11005@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=daniele@orlandi.com \
    --cc=netdev@oss.sgi.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).