public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: The current status of info, err and warn macros in kernel
Date: Sun, 26 Apr 2009 02:06:46 +0300	[thread overview]
Message-ID: <49F39786.6020303@pardus.org.tr> (raw)

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:

http://markmail.org/message/64hm5ytumcifd3iw

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.

So, is it possible that there's a Kconfig option which makes the
compilation fail on those macros?
Why am I not able to compile those modules? Am I missing something?

Thanks,

Ozan Caglayan
http://www.pardus.org.tr/eng

             reply	other threads:[~2009-04-25 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-25 23:06 Ozan Çağlayan [this message]
2009-04-26 16:21 ` The current status of info, err and warn macros in kernel Tilman Schmidt
2009-04-26 17:06   ` Ozan Çağlayan
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=49F39786.6020303@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --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