From: Greg KH <gregkh@suse.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Dmitry Torokhov <dtor_core@ameritech.net>,
Jean Delvare <khali@linux-fr.org>, Takashi Iwai <tiwai@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is platform_device_register_simple() deprecated?
Date: Wed, 12 Apr 2006 16:30:32 -0700 [thread overview]
Message-ID: <20060412233032.GA28007@suse.de> (raw)
In-Reply-To: <7724966D-F760-4075-8D69-B4B73700A9BA@kernel.crashing.org>
On Wed, Apr 12, 2006 at 06:09:48PM -0500, Kumar Gala wrote:
>
> On Apr 12, 2006, at 4:41 PM, Greg KH wrote:
>
> >On Wed, Apr 12, 2006 at 07:50:37PM +0200, Rene Herman wrote:
> >>Hi Greg, Russel, Dmitry.
> >>
> >>ALSA is using platform_device_register_simple(). Jean Delvare
> >>pointed:
> >>
> >>http://marc.theaimsgroup.com/?l=linux-kernel&m=113398060508534&w=2
> >>
> >>out, where _simple looks to be slated for removal. Is this indeed the
> >>case? ALSA isn't using the resources -- doing a manual alloc/add
> >>would
> >>not be a problem...
> >
> >Great, care to convert ALSA to use the proper api so we can remove
> >platform_device_register_simple()?
>
> Can we mark this deprecated and add it to feature-removal-schedule.txt.
Sure, I'll take a patch for that. But really, it's just easier to fix
up all callers and delete the function. It isn't anything that
feature-removal-schedule.txt should care about, as it's just the normal
API changes we do all the time.
thanks,
greg k-h
next prev parent reply other threads:[~2006-04-12 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 17:50 Is platform_device_register_simple() deprecated? Rene Herman
2006-04-12 19:18 ` Russell King
2006-04-12 21:41 ` Greg KH
2006-04-12 23:09 ` Kumar Gala
2006-04-12 23:30 ` Greg KH [this message]
2006-04-13 18:32 ` Kumar Gala
2006-04-13 2:30 ` Rene Herman
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=20060412233032.GA28007@suse.de \
--to=gregkh@suse.de \
--cc=dtor_core@ameritech.net \
--cc=galak@kernel.crashing.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tiwai@suse.de \
/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