public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXPORT_SYMBOL generates "is deprecated" noise
Date: Sun, 7 Aug 2005 20:15:42 +0100	[thread overview]
Message-ID: <20050807201541.D22977@flint.arm.linux.org.uk> (raw)
In-Reply-To: <251790000.1123438079@[10.10.2.4]>; from mbligh@mbligh.org on Sun, Aug 07, 2005 at 11:07:59AM -0700

On Sun, Aug 07, 2005 at 11:07:59AM -0700, Martin J. Bligh wrote:
> I'm getting lots of errors like this nowadays:
> 
> drivers/serial/8250.c:2651: warning: `register_serial' is deprecated 
> (declared at drivers/serial/8250.c:2607)
> 
> Which is just: "EXPORT_SYMBOL(register_serial);"
> 
> Sorry, but that's just compile-time noise, not anything useful.
> Warning on real usages of it might be handy (we can go fix the users)
> but not EXPORT_SYMBOL - we can't kill the export until the function
> goes away. The more noise we have, the harder it is to see real errors 
> and warnings.

I don't know why I bother with __deprecated - I haven't seen much
evidence of the users of these functions being cleaned up, so I
think we might as well just delete the functions and _force_ people
to fix their code.  That unfortunately seems to be the only way to
get things done in this day and age, which is rather sad if that's
what it takes to kick people into action.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  parent reply	other threads:[~2005-08-07 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 18:07 EXPORT_SYMBOL generates "is deprecated" noise Martin J. Bligh
2005-08-07 18:23 ` Adrian Bunk
2005-08-07 18:55   ` Martin J. Bligh
2005-08-07 19:06     ` Adrian Bunk
2005-08-07 19:13       ` Martin J. Bligh
2005-08-07 18:26 ` Martin J. Bligh
2005-08-08 13:46   ` Arnd Bergmann
2005-08-07 19:15 ` Russell King [this message]
2005-08-08  6:28   ` Denis Vlasenko

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=20050807201541.D22977@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.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