public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Nguyen Anh Quynh <aquynh@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Kuniyasu Suzaki <k.suzaki@aist.go.jp>
Subject: Re: [PATCH] fix calls to request_module()
Date: Thu, 11 Dec 2008 15:25:01 -0800	[thread overview]
Message-ID: <adahc5a2t2q.fsf@cisco.com> (raw)
In-Reply-To: <20081210214142.9e7b2298.akpm@linux-foundation.org> (Andrew Morton's message of "Wed, 10 Dec 2008 21:41:42 -0800")

 > I wonder if we could add a printk_stfu() which isn't declared
 > attribute(printf) and which simply calls printk.  We might still get a
 > single warning at the interface point.

That would fix the class of warnings like

	printk(char_pointer_gcc_doesnt_know_is_safe);

but therre are alsofunctions like device_create() etc etc where someone
could easily and legitimately do the same thing.

 - R.

      reply	other threads:[~2008-12-11 23:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  3:35 [PATCH] fix calls to request_module() Nguyen Anh Quynh
2008-12-11  4:01 ` Al Viro
2008-12-11  4:14   ` Nguyen Anh Quynh
2008-12-11  4:14   ` Andrew Morton
2008-12-11  4:23     ` Nguyen Anh Quynh
2008-12-11  4:40       ` Jianjun Kong
2008-12-11  4:43         ` Nguyen Anh Quynh
2008-12-11  5:02           ` Jianjun Kong
2008-12-11  5:00       ` Al Viro
2008-12-11  5:42         ` Nguyen Anh Quynh
2008-12-11  6:00           ` Al Viro
2008-12-11  6:28             ` Nguyen Anh Quynh
2008-12-11  4:49     ` Al Viro
2008-12-11  5:03       ` Roland Dreier
2008-12-11  5:41         ` Andrew Morton
2008-12-11 23:25           ` Roland Dreier [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=adahc5a2t2q.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=aquynh@gmail.com \
    --cc=k.suzaki@aist.go.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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