From: Theodore Tso <tytso@mit.edu>
To: * * <richardvoigt@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Print sysrq-m messages with KERN_INFO priority
Date: Mon, 1 Jan 2007 23:24:04 -0500 [thread overview]
Message-ID: <20070102042404.GA15718@thunk.org> (raw)
In-Reply-To: <2e59e6970612292119o38d96583ie245cb140adaafba@mail.gmail.com>
On Fri, Dec 29, 2006 at 11:19:49PM -0600, * * wrote:
> Was this patch tested?
>
> > static inline void show_node(struct zone *zone)
> > {
> > if (NUMA_BUILD)
> >- printk("Node %d ", zone_to_nid(zone));
> >+ printk(KERN_INFO, "Node %d ", zone_to_nid(zone));
>
> Here there is a comma after KERN_INFO, which does not occur elsewhere.
Thanks for noticing the typo. Yes, it's been tested and in my tree
for a while, but not on a NUMA system, so I didn't notice the problem. :-)
- Ted
prev parent reply other threads:[~2007-01-02 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 3:24 [PATCH] Print sysrq-m messages with KERN_INFO priority Theodore Ts'o
2006-12-30 4:42 ` Andrew Morton
2006-12-30 4:57 ` Dave Jones
2007-01-02 4:37 ` Theodore Tso
2007-01-02 10:33 ` Alan
2007-01-02 17:28 ` Dave Jones
2007-01-02 18:03 ` Theodore Tso
2007-01-02 18:15 ` Dave Jones
2006-12-30 5:19 ` * *
2007-01-02 4:24 ` Theodore Tso [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=20070102042404.GA15718@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardvoigt@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