From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, zippel@linux-m68k.org
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] kill i_cdev and struct char_device
Date: Sat, 8 Feb 2003 01:31:22 +0100 (MET) [thread overview]
Message-ID: <UTC200302080031.h180VMX26435.aeb@smtp.cwi.nl> (raw)
From: Roman Zippel <zippel@linux-m68k.org>
On Sat, 8 Feb 2003 Andries.Brouwer@cwi.nl wrote:
> [the whole purpose of struct block_device is to provide the link
> between a device number and a struct block_device_operations.
> struct char_device has no such function, indeed, no function at all]
Why do you think, the same shouldn't be done for char_device?
You are removing the wrong infrastructure, check how block_dev.c changed
between 2.4 and 2.5 and the same still needs to be done for char_dev.c.
Maybe. Maybe not.
I don't think such things will happen before 2.6.
It is very easy to add this code again for 2.7 if desired.
Today it is just a lot of dead code.
Andries
(And for me the question is still open whether we really want
something like struct char_device for 2.7.)
next reply other threads:[~2003-02-08 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 0:31 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 23:17 [PATCH] kill i_cdev and struct char_device Andries.Brouwer
2003-02-07 23:45 ` Roman Zippel
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=UTC200302080031.h180VMX26435.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).