From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Tilman Schmidt <t.schmidt@phoenixsoftware.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: The current status of info, err and warn macros in kernel
Date: Sun, 26 Apr 2009 20:06:52 +0300 [thread overview]
Message-ID: <49F494AC.1040708@pardus.org.tr> (raw)
In-Reply-To: <49F48A0E.30301@phoenixsoftware.de>
Tilman Schmidt wrote:
> Ozan Çağlayan schrieb:
>
>> I noticed that I can't compile some out-of-tree modules like lirc,
>> lmpcm_usb on my 2.6.30_rc* source tree.
>> The compiler aborts saying "implicit declaration of function 'info'". [...]
>> I don't think that those macros are completely removed because it seems
>> that they're still heavily in use
>> after grepping on current linus-2.6 tree.
>>
>
> Your grepping must have been inexact. info() and warn() have been removed
> completely in 2.6.29 already, and are indeed used nowhere in the current
> tree. (err() is still there, though probably not for long.)
>
> Suitable replacements are either the dev_* macros from device.h (only
> usable if there is a reliably valid device pointer available - be
> careful when using them in error handling!) or the pr_* macros from
> kernel.h with an appropriate definition of pr_fmt(f).
>
Thanks for the answer,
Regards,
next prev parent reply other threads:[~2009-04-26 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 23:06 The current status of info, err and warn macros in kernel Ozan Çağlayan
2009-04-26 16:21 ` Tilman Schmidt
2009-04-26 17:06 ` Ozan Çağlayan [this message]
2009-04-27 3:31 ` Greg KH
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=49F494AC.1040708@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=t.schmidt@phoenixsoftware.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