All of lore.kernel.org
 help / color / mirror / Atom feed
From: <pazke@orbita1.ru>
To: linux-kernel@vger.kernel.org
Subject: [PATCH][RFC][REPOST] __init_msg(x) and friends macro
Date: Mon, 28 May 2001 15:58:41 +0400	[thread overview]
Message-ID: <20010528155841.A24736@orbita1.ru> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]

Hi all,

soryy for such ugly subject line, but I already sent this patch 
to LKML and didn't get any reply.

Patch adds __init_msg (and friends) macro that places its argument 
(string constant) into corresponding .data.init section and returns
pointer to it. The goal of this patch is to allow constructions like this:

        static void __init foo(void)
	{
		printk(__init_msg(KERN_INFO "Some random long message "
				  "going to .data.init and then to bit bucket\n"));
	}

I hope this patch can save some memory and will be usefull :))

Best regards.

-- 
Andrey Panin            | Embedded systems software engineer
pazke@orbita1.ru        | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc

[-- Attachment #1.2: patch-__init_msg --]
[-- Type: text/plain, Size: 590 bytes --]

diff -ur linux.vanilla/include/linux/init.h linux/include/linux/init.h
--- linux.vanilla/include/linux/init.h	Mon May 14 15:51:20 2001
+++ linux/include/linux/init.h	Mon May 14 15:54:05 2001
@@ -155,4 +155,9 @@
 #define __devexitdata __exitdata
 #endif
 
+#define __init_msg(x) ({ static char msg[] __initdata = (x); msg; })
+#define __exit_msg(x) ({ static char msg[] __exitdata = (x); msg; })
+#define __devinit_msg(x) ({ static char msg[] __devinitdata = (x); msg; })
+#define __devexit_msg(x) ({ static char msg[] __devexitdata = (x); msg; })
+
 #endif /* _LINUX_INIT_H */

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2001-05-28 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28 11:58 pazke [this message]
2001-05-28 15:31 ` [PATCH][RFC][REPOST] __init_msg(x) and friends macro Martin Mares

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=20010528155841.A24736@orbita1.ru \
    --to=pazke@orbita1.ru \
    --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 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.