All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] [announce] new KJ web hosting
Date: Mon, 12 Jan 2004 13:18:15 +0000	[thread overview]
Message-ID: <200401121418.15029.domen@coderock.org> (raw)
In-Reply-To: <20040111193612.2b4445fc.rddunlap@osdl.org>

On Monday 12 of January 2004 13:39, Christoph Hellwig wrote:
> On Mon, Jan 12, 2004 at 12:23:39PM +0100, Domen Puncer wrote:
> > - replacing __FUNCTION__ with __func__ .
>
> No.  We had this issue a few times already. __func__ is not supported
> on older gcc releases while __FUNCTION__ works fine on all.

Ok... but at least we can remove string concatenation with __FUNCTION__ (get 
rid of warnings, and get ready for __func__):
-printk(KERN_INFO "blabla " __FUNCTION__ "\n");
+printk(KERN_INFO "blabla %s\n", __FUNCTION__);

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2004-01-12 13:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12  3:36 [Kernel-janitors] [announce] new KJ web hosting Randy.Dunlap
2004-01-12  4:43 ` Eugene Teo
2004-01-12 11:23 ` Domen Puncer
2004-01-12 12:10 ` Eugene Teo
2004-01-12 12:39 ` Christoph Hellwig
2004-01-12 13:18 ` Domen Puncer [this message]
2004-01-12 17:52 ` Randy.Dunlap
2004-01-12 18:01 ` Dave Jones
2004-01-13 11:12 ` Domen Puncer
2004-01-13 13:38 ` Dave Jones
2004-01-13 23:39 ` maximilian attems
2004-01-13 23:58 ` Randy.Dunlap
2004-01-19 20:57 ` maximilian attems
2004-01-19 23:08 ` Randy.Dunlap
2004-01-21 16:43 ` maximilian attems
2004-01-21 16:52 ` Dave Jones
2004-01-21 16:52 ` maximilian attems
2004-01-21 17:01 ` Randy.Dunlap
2004-01-21 17:37 ` maximilian attems

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=200401121418.15029.domen@coderock.org \
    --to=domen@coderock.org \
    --cc=kernel-janitors@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 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.