From: Greg KH <greg@kroah.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Couple of sysfs patches
Date: Wed, 9 Jun 2004 15:13:37 -0700 [thread overview]
Message-ID: <20040609221337.GG16653@kroah.com> (raw)
In-Reply-To: <200406090221.24739.dtor_core@ameritech.net>
On Wed, Jun 09, 2004 at 02:21:24AM -0500, Dmitry Torokhov wrote:
> Hi,
>
> I am trying to add sysfs support to the serio subsystem and I would like you
> to consider the following changes:
>
> - when registering platform device, if device id is set to -1, do not add it
> as a suffix to device's name. It can be used when there is only one device.
> The reason for change - i find that i80420 looks ugly, just i8042 is much
> better ;)
That sounds sane.
> - create platform_device_simple_releasse function that would just free memory
> occupied by platform device. Having such release routine in core allows
> drivers implementing simple platform devices not wait in module unload code
> till last reference to the device is dropped.
I'm _very_ leary of applying this. It could be abused very badly
(by putting the platform_device as the first object in the structure and
relying on this function to kfree the whole thing.) So sorry, but no.
Unless you show me a real need for it..
And as for the whitespace cleanup, why? The lack of spaces seem to be
something that the original author liked doing. There's nothing in the
kernel coding style guidelines that really mention it that I can see.
So, care to just send me the name change patch against the latest tree?
thanks,
greg k-h
next prev parent reply other threads:[~2004-06-09 22:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 7:21 [PATCH 0/3] Couple of sysfs patches Dmitry Torokhov
2004-06-09 7:22 ` [PATCH 1/3] whitespace fixes in drivers/base Dmitry Torokhov
2004-06-09 7:24 ` [PATCH 2/3] Suppress platform device suffixes Dmitry Torokhov
2004-06-09 7:25 ` [PATCH 3/3] Add platform_device_simple_release Dmitry Torokhov
2004-06-09 22:13 ` Greg KH [this message]
[not found] ` <200406091732.28684.dtor_core@ameritech.net>
2004-06-09 22:45 ` [PATCH 0/3] Couple of sysfs patches Greg KH
[not found] ` <200406091754.23303.dtor_core@ameritech.net>
2004-06-09 23:19 ` Greg KH
2004-06-10 6:40 ` Dmitry Torokhov
2004-06-10 6:42 ` [PATCH 1/3] Suppress platform device suffixes - take 2 Dmitry Torokhov
2004-06-10 6:43 ` [PATCH 2/3] Add platform_device_register_simple Dmitry Torokhov
2004-06-10 6:44 ` [PATCH 3/3] Whitespace fixes Dmitry Torokhov
2004-06-10 6:46 ` [PATCH 4/3] Allow registering device without taking bus lock Dmitry Torokhov
2004-06-10 10:14 ` Russell King
2004-06-10 16:02 ` Greg KH
2004-06-10 16:26 ` [PATCH 3/3] Whitespace fixes Greg KH
2004-06-10 10:16 ` [PATCH 2/3] Add platform_device_register_simple Russell King
[not found] ` <200406100755.59943.dtor_core@ameritech.net>
2004-06-10 13:56 ` Russell King
2004-06-10 16:04 ` Greg KH
2004-06-10 16:19 ` [PATCH 1/3] Suppress platform device suffixes - take 2 Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 14:46 [PATCH 0/3] Couple of sysfs patches Dmitry Torokhov
2004-06-10 16:06 ` Russell King
2004-06-10 16:14 ` Greg KH
2004-06-10 18:17 ` Russell King
2004-06-10 20:25 ` Russell King
2004-06-16 22:51 ` Dmitry Torokhov
2004-06-18 19:29 ` Russell King
2004-06-18 20:39 ` Greg KH
2004-06-18 19:59 Dmitry Torokhov
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=20040609221337.GG16653@kroah.com \
--to=greg@kroah.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.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