From: Tilman Schmidt <tilman@imap.cc>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Karsten Keil <kkeil@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
i4ldeveloper@listserv.isdn4linux.de,
linux-serial@vger.kernel.org, Hansjoerg Lipp <hjlipp@web.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] drivers/isdn/gigaset: new M101 driver
Date: Tue, 13 Feb 2007 00:49:58 +0100 [thread overview]
Message-ID: <45D0FD26.9030804@imap.cc> (raw)
In-Reply-To: <20070212184712.GC32607@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Am 12.02.2007 19:47 schrieb Greg KH:
>>>>> +static void gigaset_device_release(struct device *dev)
>>>>> +{
>>>>> + //FIXME anything to do? cf. platform_device_release()
>>>>> +}
> The memory of the platform device itself needs to be freed here,
> otherwise, to do it earlier would cause race conditions and oopses.
I don't do it earlier. I do it later. My platform_device structure
is part of my driver's device state structure which is freed
explicitly later after the call to platform_device_unregister().
Is that bad?
> Look at how the other platform drivers do things.
They do things differently from each other as well as from mine.
block/floppy.c, for example, just has a call to complete() there.
Anyway, in the latest version of my driver, its platform_device
release function finally does something, too: it frees
dev->platform_data and pdev->resource just in case something
might have materialized there. I hope that's ok.
Regards,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-02-12 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 21:12 [PATCH] drivers/isdn/gigaset: new M101 driver Tilman Schmidt
2007-02-02 1:13 ` Andrew Morton
2007-02-03 16:09 ` Greg KH
2007-02-04 0:26 ` Tilman Schmidt
2007-02-12 18:47 ` Greg KH
2007-02-12 23:49 ` Tilman Schmidt [this message]
2007-02-04 1:32 ` Tilman Schmidt
2007-02-04 1:56 ` Andrew Morton
2007-02-05 1:42 ` Tilman Schmidt
2007-02-05 4:58 ` Andrew Morton
2007-02-05 12:29 ` Tilman Schmidt
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=45D0FD26.9030804@imap.cc \
--to=tilman@imap.cc \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).