public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: trenn@suse.de
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	"yakui.zhao" <yakui.zhao@intel.com>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@osdl.org>,
	ALSA devel <alsa-devel@alsa-project.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sound/isa: kill pnp_resource_change.
Date: Fri, 30 Nov 2007 20:53:51 +0100	[thread overview]
Message-ID: <47506A4F.6010109@keyaccess.nl> (raw)
In-Reply-To: <1196444387.23251.332.camel@queen.suse.de>

On 30-11-07 18:39, Thomas Renninger wrote:

> On Fri, 2007-11-30 at 18:19 +0100, Rene Herman wrote:

>> Thomas Renninger is making some haste with the deprecation of the removed 
>> functions by the way -- I just saw a patch of his entering my mailbox where 
>> he says he'd in fact like them deprecated in 2.6.24 already. The ALSA 
>> removal would not seem likely to be scheduled to go to 2.6.24 yet, so I 
>> guess that won't do?
>>
>> I have no opinion on the schedule -- but Thomas, if you do, I guess you'd 
>> need to convince Jaroslav to withstand The Wrath Of Linus and ask him to 
>> push it. We can't have it deprecated (on the "spew warnings" level) with 
>> ALSA still using them in 2.6.24.
> 
> Why not?
> The intend of __deprecated is to throw some compile warnings?
> In this case it would warn on the official 2.6.24 on functions which are
> known to be reverted already for the next cycle (this should not hurt?),

It does. A clean build is not about esthetics but about quality. Warnings 
that are to be ignored hide warnings that are not to be, not just in the 
sense of the output but due to humans actively tuning out the noise after 
just a few. I'd hate for sound/isa to add to the noise.

> it's more for drivers building against kernel headers getting noticed as
> soon as possible...
> 
> If this is not added to 2.6.24, the funcs should live there for another
> kernel cycle just to not print some irrelevant warnings at compile time
> things are slowed down...

This makes sense if someone told you that the deprecation period for 
exported symbols is one kernel cycle but who did?

Anyways, two things:

The number of out of tree users of these symbols is very close to zero and 
quite possibly if not likely _at_ zero after I've cleaned up the couple of 
half-hearted ALSA ISAPnP drivers that I keep in a few local branches here.

As such, and given that removing them apparently clears the path for a long 
overdue and welcome PnP cleanup, simply yanking them soon would get my ack.

Second, as said, speak to Jaroslav as well I guess.

> This is also in vanilla and lives there for some time?:
> kernel/power/pm.c:205: warning: ‘pm_register’ is deprecated (declared at kernel/power/pm.c:64)
> kernel/power/pm.c:205: warning: ‘pm_register’ is deprecated (declared at kernel/power/pm.c:64)
> kernel/power/pm.c:206: warning: ‘pm_send_all’ is deprecated (declared at kernel/power/pm.c:180)
> kernel/power/pm.c:206: warning: ‘pm_send_all’ is deprecated (declared at kernel/power/pm.c:180)

Exactly, and serves as a perfect reminder of why noone should ever be 
allowed to deprecate anything until after removing all in tree users.

Rene.

           reply	other threads:[~2007-11-30 19:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1196444387.23251.332.camel@queen.suse.de>]

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=47506A4F.6010109@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=shaohua.li@intel.com \
    --cc=tiwai@suse.de \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.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