All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
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:24:55 +0200	[thread overview]
Message-ID: <200510250024.56088.ak@suse.de> (raw)
In-Reply-To: <200510242333.05366.daniele@orlandi.com>

On Monday 24 October 2005 23:33, Daniele Orlandi wrote:

> 
> > Normally Linux doesn't pre-allocate ABIs for out of tree code, mostly
> > because it is not guaranteed that the interface won't change there.
> 
> Could you clarify? What interface do you fear that could change?

Any interface implemented by your out of tree code for which you're
requesting to reserve constants.

-Andi

      parent reply	other threads:[~2005-10-24 22:24 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
2005-10-24 22:58           ` Daniele Orlandi
2005-10-24 22:24     ` 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=200510250024.56088.ak@suse.de \
    --to=ak@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.