All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Joseph Pingenot <trelane@digitasaru.net>,
	linux-kernel@vger.kernel.org,
	Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: Please open sysfs symbols to proprietary modules
Date: Wed, 2 Feb 2005 20:57:36 -0800	[thread overview]
Message-ID: <20050203045736.GA17820@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0502021950040.19812@localhost.localdomain>

On Wed, Feb 02, 2005 at 08:13:15PM -0500, Pavel Roskin wrote:
> 
> I won't open all details, but suppose I want the bridge to handle certain 
> frames in a special way, just like BPDU frames are handled if STP is 
> enabled.  There is a hook for that already - see br_handle_frame_hook. 
> The proprietary module would just have to change it.

Why use Linux if you want to make a proprietary module?  Why not use
another operating system that is more suited toward such usage.  The
Linux kernel certainly is not such a system.

greg k-h

  parent reply	other threads:[~2005-02-03  5:00 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 22:56 Please open sysfs symbols to proprietary modules Pavel Roskin
2005-02-02 23:07 ` Greg KH
2005-02-02 23:23 ` Patrick Mochel
2005-02-02 23:29   ` Greg KH
2005-02-03  0:07     ` Pavel Roskin
2005-02-03  0:30       ` Greg KH
2005-02-03  4:54         ` Zan Lynx
2005-02-03  5:07           ` Greg KH
2005-02-03  8:59           ` Helge Hafting
2005-02-03 15:12           ` Alan Cox
2005-02-03 17:26             ` Theodore Ts'o
2005-02-03 13:47         ` linux-os
2005-02-04 16:05       ` David Woodhouse
2005-02-03  0:09 ` Joseph Pingenot
2005-02-03  1:13   ` Pavel Roskin
2005-02-03  2:50     ` Kyle Moffett
2005-02-03  3:17       ` Jon Masters
2005-02-06  7:24       ` Lee Revell
2005-02-07 16:05         ` Chris Friesen
2005-02-07 16:55           ` linux-os
2005-02-07 18:58             ` jerome lacoste
2005-02-07 19:35               ` linux-os
2005-02-07 16:55           ` Randy.Dunlap
2005-02-08  1:40             ` Horst von Brand
2005-02-03  4:57     ` Greg KH [this message]
2005-02-03  8:41 ` Arjan van de Ven
2005-02-03 21:00 ` Ben Greear
2005-02-04  9:20 ` Andrew Morton
2005-02-04  9:40   ` Arjan van de Ven
2005-02-15  1:41   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-02-03  4:08 Jonathan A. George
2005-02-03  5:07 ` Kyle Moffett
2005-02-03 12:30 Jonathan A. George
2005-02-04 15:16 ` Adrian Bunk
2005-02-17 23:13 parker
2005-02-18  3:32 ` Chris Friesen
2005-02-18 13:13 ` Arjan van de Ven

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=20050203045736.GA17820@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=proski@gnu.org \
    --cc=trelane@digitasaru.net \
    /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.