mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: linux-kernel@vger.kernel.org
Cc: trivial@kernel.org, Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 0/4] Fix some spurious errors at bootup
Date: Sat,  8 Mar 2014 10:58:11 -0800	[thread overview]
Message-ID: <cover.1394304585.git.luto@amacapital.net> (raw)

A bunch of drivers that my system loads spew out KERN_ERR or
severity-less messages at startup.  These message are not errors.  Fix
them.

Andy Lutomirski (4):
  mei: Don't log an error when the MEI device is quirked off
  megaraid: Downgrade success messages from KERN_ERR to dev_dbg
  sr: Add a missing KERN_INFO
  raid6: Add severity levels to raid6 initialization messages

 drivers/misc/mei/pci-me.c                   |  2 +-
 drivers/scsi/megaraid/megaraid_sas_base.c   |  2 +-
 drivers/scsi/megaraid/megaraid_sas_fusion.c |  2 +-
 drivers/scsi/sr.c                           |  3 ++-
 lib/raid6/algos.c                           | 13 +++++++------
 5 files changed, 12 insertions(+), 10 deletions(-)

-- 
1.8.5.3


             reply	other threads:[~2014-03-08 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08 18:58 Andy Lutomirski [this message]
2014-03-08 18:58 ` [PATCH 1/4] mei: Don't log an error when the MEI device is quirked off Andy Lutomirski
2014-03-11 10:03   ` Winkler, Tomas
2014-03-11 22:17     ` Andy Lutomirski
2014-03-11 22:33       ` Winkler, Tomas
2014-03-08 18:58 ` [PATCH 2/4] megaraid: Downgrade success messages from KERN_ERR to dev_dbg Andy Lutomirski
2014-03-08 18:58 ` [PATCH 3/4] sr: Add a missing KERN_INFO Andy Lutomirski
2014-03-08 18:58 ` [PATCH 4/4] raid6: Add severity levels to raid6 initialization messages Andy Lutomirski
2014-03-08 19:14   ` Paul Bolle
2014-03-11 22:22     ` Andy Lutomirski

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=cover.1394304585.git.luto@amacapital.net \
    --to=luto@amacapital.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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