mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@mbligh.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXPORT_SYMBOL generates "is deprecated" noise
Date: Sun, 07 Aug 2005 11:26:45 -0700	[thread overview]
Message-ID: <253710000.1123439204@[10.10.2.4]> (raw)
In-Reply-To: <251790000.1123438079@[10.10.2.4]>

--"Martin J. Bligh" <mbligh@mbligh.org> wrote (on Sunday, August 07, 2005 11:07:59 -0700):

> 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 took a quick poke around, but can't see what generates this stuff.
> What is doing these checks, and can we please make an exception for
> EXPORT_SYMBOL (and EXPORT_SYMBOL_GPL) somehow?

Oh, I'm being an idiot and looking at the wrong tree. It's __deprecated,
but I still can't think of a clean way to locally undefine that for
just EXPORT_SYMBOL.

M.


  parent reply	other threads:[~2005-08-07 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 18:07 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 [this message]
2005-08-08 13:46   ` Arnd Bergmann
2005-08-07 19:15 ` Russell King
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='253710000.1123439204@[10.10.2.4]' \
    --to=mbligh@mbligh.org \
    --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

all inboxes | Powered by JetHome®