From: "Shaheed R. Haque" <srhaque@iee.org>
To: <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>, <with@dsl.pipex.com>
Subject: Re: Re: [RFC] Device class rework [0/5]
Date: Wed, 23 Apr 2003 08:54:04 +0100 [thread overview]
Message-ID: <1051084444.3ea6469c044ef@netmail.pipex.net> (raw)
Hi Greg,
I support the intent of this patch, but would it not be a better idea to rename
the struct something like "device_class"? Rationale:
1. See the title of your patch (!!)
2. The word "class" is too generic and conveys no sense that is is to do with
devices.
3. I know that C++ is never going to make it into the kernel, but...
Thanks, Shaheed
next reply other threads:[~2003-04-23 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 7:54 Shaheed R. Haque [this message]
2003-04-23 16:00 ` [RFC] Device class rework [0/5] Greg KH
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=1051084444.3ea6469c044ef@netmail.pipex.net \
--to=srhaque@iee.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=with@dsl.pipex.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;
as well as URLs for NNTP newsgroup(s).