From: Jan Kara <jack@suse.cz>
To: Joe Perches <joe@perches.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, NamJae Jeon <linkinjeon@gmail.com>
Subject: Re: [PATCH 4/6] udf: Convert printks to pr_<level>
Date: Mon, 10 Oct 2011 19:40:58 +0200 [thread overview]
Message-ID: <20111010174058.GJ3944@quack.suse.cz> (raw)
In-Reply-To: <1318267510.27825.20.camel@Joe-Laptop>
On Mon 10-10-11 10:25:10, Joe Perches wrote:
> On Mon, 2011-10-10 at 18:41 +0200, Jan Kara wrote:
> > On Mon 10-10-11 08:23:34, Joe Perches wrote:
> > > I forgot to mention that udf_err emits at KERN_CRIT.
> > > I think that's not good.
> > I've changed udf_err() to call pr_err() because
> > KERN_CRIT is really too much.
>
> If this means you applied it or applied it with
> modifications, I think it'd be good to either
> reply to the 0/n message with something like
> "applied to my tree", or reply to each message
> as appropriate.
Sure, that's what I wanted to do but I first wanted to test what I have,
stumbled across an issue with patch 1 which delayed me a bit...
> That reply lets other people like NamJae proceed
> appropriately. Otherwise, it's left to some
> pull request or patch series posted by you
> potentially months later to figure out what's
> current.
>
> Is there a udf git tree?
On kernel.org which is down... I didn't bother to setup some other place
yet.
> The stuff on sourceforge is not current
> and the MAINTAINERS W: entry doesn't work.
Actually, the link is ancient and I don't use SF for UDF development so
I've added a patch to my tree which removes the link.
>
> Maybe:
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 644894a..58eb5f1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6624,7 +6624,7 @@ F: drivers/net/ethernet/8390/ne-h8300.c
>
> UDF FILESYSTEM
> M: Jan Kara <jack@suse.cz>
> -W: http://linux-udf.sourceforge.net
> +W: http://sourceforge.net/projects/linux-udf/develop
> S: Maintained
> F: Documentation/filesystems/udf.txt
> F: fs/udf/
>
> cheers, Joe
>
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-10-10 17:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 13:53 [PATCH 1/2 v3] udf : enable error print in udf_read_tagged() Namjae Jeon
2011-10-05 22:08 ` Jan Kara
2011-10-05 22:19 ` Joe Perches
2011-10-06 21:41 ` Jan Kara
2011-10-09 3:16 ` NamJae Jeon
2011-10-09 3:29 ` Joe Perches
2011-10-09 4:44 ` NamJae Jeon
2011-10-09 4:56 ` Joe Perches
2011-10-09 6:25 ` NamJae Jeon
2011-10-09 14:07 ` NamJae Jeon
2011-10-10 8:08 ` [PATCH 0/6] udf: Change some KERN_<level>s and logging neatening Joe Perches
2011-10-10 8:08 ` [PATCH 1/6] udf: Promote some debugging messages to udf_error Joe Perches
2011-10-10 10:06 ` NamJae Jeon
2011-10-10 17:32 ` Jan Kara
2011-10-10 8:08 ` [PATCH 2/6] udf: Rename udf_error to udf_err Joe Perches
2011-10-10 10:18 ` NamJae Jeon
2011-10-10 8:08 ` [PATCH 3/6] udf: Rename udf_warn to udf_warn Joe Perches
2011-10-10 10:18 ` NamJae Jeon
2011-10-10 18:25 ` Paul Bolle
2011-10-10 18:27 ` Joe Perches
2011-10-10 8:08 ` [PATCH 4/6] udf: Convert printks to pr_<level> Joe Perches
2011-10-10 10:21 ` NamJae Jeon
2011-10-10 14:59 ` Jan Kara
2011-10-10 15:20 ` Joe Perches
2011-10-10 15:23 ` Joe Perches
2011-10-10 16:41 ` Jan Kara
2011-10-10 17:25 ` Joe Perches
2011-10-10 17:40 ` Jan Kara [this message]
2011-10-10 8:08 ` [PATCH 5/6] udf: Neaten logging output, use vsprintf extension %pV Joe Perches
2011-10-10 10:22 ` NamJae Jeon
2011-10-10 15:04 ` Jan Kara
2011-10-10 15:20 ` Joe Perches
2011-10-10 8:08 ` [PATCH 6/6] udf: Neaten udf_debug uses Joe Perches
2011-10-10 10:23 ` NamJae Jeon
2011-10-10 10:24 ` [PATCH 0/6] udf: Change some KERN_<level>s and logging neatening NamJae Jeon
2011-10-10 17:47 ` 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=20111010174058.GJ3944@quack.suse.cz \
--to=jack@suse.cz \
--cc=joe@perches.com \
--cc=linkinjeon@gmail.com \
--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
Powered by JetHome