From: Christoph Hellwig <hch@infradead.org>
To: ilya@theIlya.com
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: O2 VICE support
Date: Wed, 11 Dec 2002 22:45:07 +0000 [thread overview]
Message-ID: <20021211224507.A6807@infradead.org> (raw)
In-Reply-To: <20021211221629.GP609@gateway.total-knowledge.com>; from ilya@theIlya.com on Wed, Dec 11, 2002 at 02:16:29PM -0800
On Wed, Dec 11, 2002 at 02:16:29PM -0800, ilya@theIlya.com wrote:
> > > + if (!filp->private_data) {
> > > + filp->private_data = vice_device;
> > > + }
> >
> > filp->private_data can't be set.
> ???
> I can live without using it of course, since it isn't currently possible to have
> more then one instance of VICE in same machine, but theoretical possibility does
> exist. Where should I pass information about which specific device current
> call is?
Sorry if that sentence was confusing. I meant it can't be already set in
->open so the if is superflous.
> > > +void vice_cleanup_module(void)
> > > +{
> > > +#ifndef CONFIG_DEVFS_FS
> > > + /* cleanup_module is never called if registering failed */
> > > + unregister_chrdev(vice_major, "vice");
> > > +#endif
> >
> > Umm, just because someone makes the mistake of enabling devfs he
> > doesn't have to use it.. :)
> I'm not buying that one :)
You can have CONFIG_DEVFS_FS set but devfs not mounted and used.
Thus #ifndef CONFIG_DEVFS_FS code is a very bad idea.
next prev parent reply other threads:[~2002-12-11 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 19:11 O2 VICE support ilya
2002-12-11 13:38 ` Christoph Hellwig
2002-12-11 22:16 ` ilya
2002-12-11 22:45 ` Christoph Hellwig [this message]
2002-12-11 22:46 ` Juan Quintela
2002-12-22 9:20 ` Geert Uytterhoeven
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=20021211224507.A6807@infradead.org \
--to=hch@infradead.org \
--cc=ilya@theIlya.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox