mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: TProvoni@aol.com
Cc: martillo@telfordtools.com, marcelo@conectiva.com.br,
	linux-kernel@vger.kernel.org, linux@auroratech.com,
	frank@auroratech.com
Subject: Re: 2.4.19-pre8 non-kernel files in wan/8253x
Date: Fri, 17 May 2002 08:29:34 +1000	[thread overview]
Message-ID: <2888.1021588174@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 16 May 2002 11:07:15 EDT." <141.e9270f3.2a152523@aol.com>

On Thu, 16 May 2002 11:07:15 EDT, 
TProvoni@aol.com wrote:
>In a message dated 5/16/2002 3:57:52 AM Eastern Daylight Time, 
>kaos@ocs.com.au writes:
>> drivers/net/wan/8253x/Makefile contains these lines
>> 
>> 8253xcfg: 8253xcfg.c
>>         $(CC)  -o 8253xcfg $(EXTRA_CFLAGS) -U__KERNEL__ 8253xcfg.c
>> 
>> 8253xmac: 8253xmac.c
>>         $(CC)  -o 8253xmac $(EXTRA_CFLAGS) -U__KERNEL__ 8253xmac.c
>> 
>> 8253xspeed: 8253xspeed.c
>>         $(CC)  -o 8253xspeed $(EXTRA_CFLAGS) -U__KERNEL__ 8253xspeed.c
>> 
>> 8253xpeer: 8253xpeer.c
>>         $(CC)  -o 8253xpeer $(EXTRA_CFLAGS) -U__KERNEL__ 8253xpeer.c
>> 
>> eprom9050: eprom9050.c
>>         $(CC)  -o eprom9050 $(EXTRA_CFLAGS) -U__KERNEL__ eprom9050.c
>> 
>> All of those .c files are user space utilities, they do not fit the
>> kernel build system and do not belong in the kernel.  Please move these
>> files to a separate user space package and delete from 2.4.19-pre*.
>
>I think there needs to be some way to guarantee that these last two programs
>are available whenever the driver is included with a kernel.

User space programs do not belong in the kernel.  They belong in a user
space package, like all the other device tuning programs.  The kernel
documentation for your driver points to the user space package.


       reply	other threads:[~2002-05-16 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <141.e9270f3.2a152523@aol.com>
2002-05-16 22:29 ` Keith Owens [this message]
2002-05-16  7:57 Keith Owens

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=2888.1021588174@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=TProvoni@aol.com \
    --cc=frank@auroratech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@auroratech.com \
    --cc=marcelo@conectiva.com.br \
    --cc=martillo@telfordtools.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

all inboxes | Powered by JetHome®