linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Nazarewicz" <mina86@mina86.com>
To: "Michał Nazarewicz" <mnazarewicz@gmail.com>,
	"Dave Hansen" <dave@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] break out page allocation warning code
Date: Mon, 11 Apr 2011 12:20:49 +0200	[thread overview]
Message-ID: <op.vtrq0zac3l0zgt@mnazarewicz-glaptop> (raw)
In-Reply-To: <1302296522.7286.1197.camel@nimitz>

>> On Apr 8, 2011 10:23 PM, "Dave Hansen" <dave@linux.vnet.ibm.com> wrote:
>>> +       if (fmt) {
>>> +               printk(KERN_WARNING);
>>> +               va_start(args, fmt);
>>> +               r = vprintk(fmt, args);
>>> +               va_end(args);
>>> +       }

> On Fri, 2011-04-08 at 22:54 +0200, Michał Nazarewicz wrote:
>> Could we make the "printk(KERN_WARNING);" go away and require caller
>> to specify level?

On Fri, 08 Apr 2011 23:02:02 +0200, Dave Hansen wrote:
> The core problem is this: I want two lines of output: one for the
> order/mode gunk, and one for the user-specified message.
>
> If we have the user pass in a string for the printk() level, we're stuck
> doing what I have here.  If we have them _prepend_ it to the "fmt"
> string, then it's harder to figure out below.  I guess we could fish in
> the string for it.

This is a bit unfortunate, but that's what I was worried anyway.  I guess
creating a macro which automatically prepends format  with KERN_WARNING
would solve the issue but that's probably not the most elegant solution.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michal "mina86" Nazarewicz    (o o)
ooo +-----<email/xmpp: mnazarewicz@google.com>-----ooO--(_)--Ooo--

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-04-11 10:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 20:22 Dave Hansen
2011-04-08 20:22 ` [PATCH 2/2] print vmalloc() state after allocation failures Dave Hansen
2011-04-08 20:39   ` David Rientjes
2011-04-08 20:47     ` Dave Hansen
2011-04-08 20:37 ` [PATCH 1/2] break out page allocation warning code David Rientjes
2011-04-08 20:43   ` Dave Hansen
2011-04-08 20:54 ` Michał Nazarewicz
2011-04-08 21:02   ` Dave Hansen
2011-04-11 10:20     ` Michal Nazarewicz [this message]
2011-04-15 17:04 Dave Hansen
2011-04-17  0:02 ` David Rientjes
2011-04-18 15:10   ` Dave Hansen
2011-04-18 20:25     ` David Rientjes
2011-04-18 20:57       ` Dave Hansen
2011-04-19 21:23         ` David Rientjes
2011-04-18 21:03       ` Dave Hansen
2011-04-18 21:22       ` Dave Hansen
2011-04-19  0:44         ` KOSAKI Motohiro
2011-04-19 21:21           ` David Rientjes
2011-04-20  0:39             ` KOSAKI Motohiro
2011-04-20 20:24               ` David Rientjes
2011-04-20 20:34                 ` john stultz
2011-04-21  1:29                   ` KOSAKI Motohiro
2011-04-25  4:21                     ` KOSAKI Motohiro
2011-04-26 19:27                     ` john stultz
2011-04-27 23:51                       ` David Rientjes
2011-04-28  0:32                         ` john stultz
2011-04-28  1:29                           ` john stultz
2011-04-28 22:48                             ` David Rientjes
2011-04-28 23:48                               ` john stultz
2011-04-29  0:04                                 ` john stultz
2011-04-26 21:25                     ` john stultz
2011-04-28  3:05                       ` KOSAKI Motohiro
2011-04-20  1:41             ` Dave Hansen
2011-04-20  1:50               ` KOSAKI Motohiro
2011-04-20  2:19                 ` KOSAKI Motohiro
2011-04-20  2:46                   ` Dave Hansen
2011-04-19 16:21 Dave Hansen

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=op.vtrq0zac3l0zgt@mnazarewicz-glaptop \
    --to=mina86@mina86.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mnazarewicz@gmail.com \
    /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