From: Greg KH <greg@kroah.com>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
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:31:43 -0700 [thread overview]
Message-ID: <20090427033143.GA23388@kroah.com> (raw)
In-Reply-To: <49F39786.6020303@pardus.org.tr>
On Sun, Apr 26, 2009 at 02:06:46AM +0300, Ozan Çağlayan wrote:
> Hi,
>
> 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
> googled and found the following thread
> in linux-next mailing list:
Like was pointed out, they are really gone now. They were usb-only
functions, that didn't make sense anymore, and lots of other drivers
were using them instead.
Convert to use the dev_* functions instead, those are also backwards
compatible, which should make your life a bit easier.
good luck,
greg k-h
prev parent reply other threads:[~2009-04-27 3:39 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
2009-04-27 3:31 ` Greg KH [this message]
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=20090427033143.GA23388@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.