netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ivecera@redhat.com
Cc: netdev@vger.kernel.org, sathya.perla@emulex.com,
	subbu.seetharaman@emulex.com, ajit.khaparde@emulex.com
Subject: Re: [PATCH net-next] be2net: don't use dev_err when AER enabling fails
Date: Tue, 30 Jul 2013 00:00:41 -0700 (PDT)	[thread overview]
Message-ID: <20130730.000041.2001900161264941490.davem@davemloft.net> (raw)
In-Reply-To: <1374761455-28193-1-git-send-email-ivecera@redhat.com>

From: Ivan Vecera <ivecera@redhat.com>
Date: Thu, 25 Jul 2013 16:10:55 +0200

> The driver uses dev_err when enabling of AER fails (e.g. PCIe AER is not
> supported). The dev_info is more appropriate to avoid console pollution.
> 
> Cc: sathya.perla@emulex.com
> Cc: subbu.seetharaman@emulex.com
> Cc: ajit.khaparde@emulex.com
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>

Applied, thanks.

      reply	other threads:[~2013-07-30  7:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 14:10 [PATCH net-next] be2net: don't use dev_err when AER enabling fails Ivan Vecera
2013-07-30  7:00 ` David Miller [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=20130730.000041.2001900161264941490.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ajit.khaparde@emulex.com \
    --cc=ivecera@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sathya.perla@emulex.com \
    --cc=subbu.seetharaman@emulex.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;
as well as URLs for NNTP newsgroup(s).