From: Martin Bligh <mbligh@mbligh.org>
To: Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] add newline to nfs dprintk
Date: Wed, 02 Aug 2006 13:59:39 -0700 [thread overview]
Message-ID: <44D1123B.2000602@mbligh.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Add missing \n to dprintk
(attatched as well, cause thunderbird is pants)
Signed-off-by: mbligh@google.com
diff -aurpN -X /home/mbligh/.diff.exclude
linux-2.6.18-rc3/fs/lockd/clntlock.c
linux-2.6.18-rc3-nfs_printk/fs/lockd/clntlock.c
--- linux-2.6.18-rc3/fs/lockd/clntlock.c 2006-07-31
10:18:54.000000000 -0700
+++ linux-2.6.18-rc3-nfs_printk/fs/lockd/clntlock.c 2006-08-02
13:56:39.000000000 -0700
@@ -160,7 +160,7 @@ static void nlmclnt_prepare_reclaim(stru
*/
list_splice_init(&host->h_granted, &host->h_reclaim);
- dprintk("NLM: reclaiming locks for host %s", host->h_name);
+ dprintk("NLM: reclaiming locks for host %s\n", host->h_name);
}
static void nlmclnt_finish_reclaim(struct nlm_host *host)
[-- Attachment #2: linux-2.6.18-rc3-nfs_printk --]
[-- Type: text/plain, Size: 668 bytes --]
Add missing \n to dprintk
Signed-off-by: mbligh@google.com
diff -aurpN -X /home/mbligh/.diff.exclude linux-2.6.18-rc3/fs/lockd/clntlock.c linux-2.6.18-rc3-nfs_printk/fs/lockd/clntlock.c
--- linux-2.6.18-rc3/fs/lockd/clntlock.c 2006-07-31 10:18:54.000000000 -0700
+++ linux-2.6.18-rc3-nfs_printk/fs/lockd/clntlock.c 2006-08-02 13:56:39.000000000 -0700
@@ -160,7 +160,7 @@ static void nlmclnt_prepare_reclaim(stru
*/
list_splice_init(&host->h_granted, &host->h_reclaim);
- dprintk("NLM: reclaiming locks for host %s", host->h_name);
+ dprintk("NLM: reclaiming locks for host %s\n", host->h_name);
}
static void nlmclnt_finish_reclaim(struct nlm_host *host)
reply other threads:[~2006-08-02 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44D1123B.2000602@mbligh.org \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox