From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>, NamJae Jeon <linkinjeon@gmail.com>
Subject: [PATCH 0/6] udf: Message printing cleanup (v2)
Date: Mon, 10 Oct 2011 19:50:36 +0200 [thread overview]
Message-ID: <1318269042-16806-1-git-send-email-jack@suse.cz> (raw)
Hello,
these are patches from Joe and NamJae which I currently carry in my tree.
Honza
next reply other threads:[~2011-10-10 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 17:50 Jan Kara [this message]
2011-10-10 17:50 ` [PATCH 1/6] udf: Promote some debugging messages to udf_error Jan Kara
2011-10-10 17:50 ` [PATCH 2/6] udf: Rename udf_error to udf_err Jan Kara
2011-10-10 17:50 ` [PATCH 3/6] udf: Rename udf_warning to udf_warn Jan Kara
2011-10-10 17:50 ` [PATCH 4/6] udf: Convert printks to pr_<level> Jan Kara
2011-10-10 17:50 ` [PATCH 5/6] udf: Neaten logging output, use vsprintf extension %pV Jan Kara
2011-10-10 17:50 ` [PATCH 6/6] udf: Neaten udf_debug uses Jan Kara
2011-10-10 18:16 ` [PATCH 0/6] udf: Message printing cleanup (v2) Joe Perches
2011-10-10 18:24 ` Jan Kara
2011-10-10 23:02 ` NamJae Jeon
2011-10-10 23:17 ` Jan Kara
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=1318269042-16806-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=joe@perches.com \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).