From: Kay Sievers <kay.sievers@vrfy.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH] Remove "decl_subsys_name" macro and single usage of it.
Date: Thu, 15 Mar 2007 14:08:07 +0100 [thread overview]
Message-ID: <1173964087.5099.14.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703150630270.23698@localhost.localdomain>
On Thu, 2007-03-15 at 08:52 -0400, Robert P. J. Day wrote:
> On Thu, 15 Mar 2007, Kay Sievers wrote:
>
> > On 3/1/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > >
> > > Remove the macro "decl_subsys_name" which can be used to declare a
> > > sysfs subsystem, along with the single invocation of it in the source
> > > tree, since there appears to be little value in creating a subsystem
> > > whose subsystem name differs from its structure name. Everyone else
> > > just uses "decl_subsys".
> >
> > Sometimes you want shorter variable names as the created objects in
> > sysfs, because the 80 columns limit of the kernel source makes long
> > variable names pretty inconvenient.
> > And all these decl_* macros, obviously can't create any names that
> > contain '-', which is pretty annoying. There is also a user in the
> > experimental patches in Greg's tree. Please leave it there for now.
>
> no problem but that patch *was* based on a suggestion by greg in the
> first place. i'm guessing he just forgot. :-)
A cleanup of the driver-core source is long overdue, that's why we like
everything that goes away here, that isn't really needed. :)
In the end, we should probably just get rid of the whole "struct
subsystem". We can move the lock to the kset and ditch the whole weird
idea of a "subsystem", which is nothing but a collection of ksets, which
the object model can handle without "struct subsystem" just fine.
Thanks,
Kay
prev parent reply other threads:[~2007-03-15 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:09 Robert P. J. Day
2007-03-15 7:25 ` Greg KH
2007-03-15 10:22 ` Kay Sievers
2007-03-15 12:52 ` Robert P. J. Day
2007-03-15 13:08 ` Kay Sievers [this message]
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=1173964087.5099.14.camel@pim.off.vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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
all inboxes | Powered by JetHome®