From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Joe Perches <joe@perches.com>, Anton Altaparmakov <anton@tuxera.com>
Cc: linux-ntfs-dev@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Liqin Chen <liqin.linux@gmail.com>,
"lennox.wu@gmail.com >> Lennox Wu" <lennox.wu@gmail.com>
Subject: Re: [PATCH] fs/ntfs: Use '%tx' instead of '%zx'
Date: Mon, 23 Jun 2014 11:00:10 +0800 [thread overview]
Message-ID: <53A7983A.9000105@gmail.com> (raw)
In-Reply-To: <1403487989.18747.30.camel@joe-AO725>
On 06/23/2014 09:46 AM, Joe Perches wrote:
> Please make sure to cc the specific maintainer
>
> $ ./scripts/get_maintainer.pl -f fs/ntfs/
> Anton Altaparmakov <anton@tuxera.com> (supporter:NTFS FILESYSTEM)
> linux-ntfs-dev@lists.sourceforge.net (open list:NTFS FILESYSTEM)
> linux-kernel@vger.kernel.org (open list)
>
> (cc'ing Anton)
>
Yes, I have sent to specific maintainer.
> btw Anton, it seems ntfs_debug does not terminate
> messages with a "\n". That means that messages
> could be interleaved with other output.
>
> Maybe this patch as well as Chen Gang's below should be applied
> ---
> fs/ntfs/debug.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ntfs/debug.c b/fs/ntfs/debug.c
> index dd6103c..1e824f0 100644
> --- a/fs/ntfs/debug.c
> +++ b/fs/ntfs/debug.c
> @@ -126,7 +126,8 @@ void __ntfs_debug (const char *file, int line, const char *function,
> va_start(args, fmt);
> vaf.fmt = fmt;
> vaf.va = &args;
> - pr_debug("(%s, %d): %s(): %pV", file, line, flen ? function : "", &vaf);
> + pr_debug("(%s, %d): %s(): %pV\n",
> + file, line, flen ? function : "", &vaf);
> va_end(args);
> }
>
Hmm... at least, the patch above is fine to me.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2014-06-23 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 1:35 Chen Gang
2014-06-23 1:46 ` Joe Perches
2014-06-23 3:00 ` Chen Gang [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=53A7983A.9000105@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=anton@tuxera.com \
--cc=joe@perches.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=liqin.linux@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
all inboxes | Powered by JetHome®