mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Pásztor Szilárd" <silicon@inf.bme.hu>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	Adrian Bunk <bunk@fs.tum.de>
Subject: Re: [2.5 patch] let COMX depend on PROC_FS
Date: Tue, 10 Jun 2003 14:26:14 +0100	[thread overview]
Message-ID: <20030610142614.A25666@infradead.org> (raw)
In-Reply-To: <Pine.GSO.4.00.10306101347450.1700-100000@kempelen.iit.bme.hu>; from silicon@inf.bme.hu on Tue, Jun 10, 2003 at 01:55:22PM +0200

On Tue, Jun 10, 2003 at 01:55:22PM +0200, Pásztor Szilárd wrote:
> The drivers are used by some hundreds of cards today but we tell users to
> get the small kernelpatch from www.itc.hu and the patch, among other things,
> exports proc_get_inode. There was a process to integrate the patch into the
> mainstream kernel last year but, due to lack of time on my part, it was
> suspended. I hope to be able to pick the line up again and clean things up.

So what about fixing it instead?  The usage of proc_get_inode is broken
and so is the whole profs mess in the comx driver.  If you want to keep
the API you need to add a ramfs-style filesystem instead of abusing
procfs.


  reply	other threads:[~2003-06-10 13:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 14:40 Adrian Bunk
2003-06-08 16:49 ` Christoph Hellwig
2003-06-08 16:56   ` Adrian Bunk
2003-06-08 16:58     ` Christoph Hellwig
2003-06-10 11:55       ` Pásztor Szilárd
2003-06-10 13:26         ` Christoph Hellwig [this message]
2003-06-10 13:51           ` Pásztor Szilárd
2003-06-10 13:57             ` Christoph Hellwig
2003-06-10 14:11               ` Pásztor Szilárd
2003-06-10 14:14           ` viro

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=20030610142614.A25666@infradead.org \
    --to=hch@infradead.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=silicon@inf.bme.hu \
    /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®