linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH] jbd2: Revise KERN_EMERG error messages
Date: Mon, 2 Dec 2013 09:55:17 -0500	[thread overview]
Message-ID: <20131202145517.GC25294@thunk.org> (raw)
In-Reply-To: <1385420357-30944-2-git-send-email-jack@suse.cz>

On Mon, Nov 25, 2013 at 11:59:17PM +0100, Jan Kara wrote:
> Some of KERN_EMERG printk messages do not really deserve this log level
> and the one in log_wait_commit() is even rather useless (the journal has
> been previously aborted and *that* is where we should have been
> complaining). So make some messages just KERN_ERR and remove the useless
> message.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>

Thanks, applied.

						- Ted

      reply	other threads:[~2013-12-02 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 22:59 [PATCH] jbd: Revise KERN_EMERG error messages Jan Kara
2013-11-25 22:59 ` [PATCH] jbd2: " Jan Kara
2013-12-02 14:55   ` Theodore Ts'o [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=20131202145517.GC25294@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    /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).