LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Karl Dahlke <eklhad@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where to put adapters
Date: Tue, 19 Feb 2008 20:24:47 +0100	[thread overview]
Message-ID: <20080219192447.GB11948@uranus.ravnborg.org> (raw)
In-Reply-To: <20080119080148.eklhad@comcast.net>

On Tue, Feb 19, 2008 at 08:01:48AM -0500, Karl Dahlke wrote:
> Now that notifiers are in, (yay!), people are going to start writing adapters
> for visually and motor impaired individuals.
> I suggest we place them in drivers/adapters in the source tree,
> and I suggest they put their virtual files in the directory /proc/adapters,
> which would be created via fs/proc/root.c as part of the /proc file system.

/proc is for processes (and was in the past used for all sort of crap).
So without knowing what an adapter is in this context /proc
seems to be a bad choice.

	Sam

  reply	other threads:[~2008-02-19 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 13:01 Karl Dahlke
2008-02-19 19:24 ` Sam Ravnborg [this message]
2008-02-19 19:37 ` Jan Engelhardt

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=20080219192447.GB11948@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=eklhad@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Where to put adapters' \
    /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

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).