Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bkenward@solarflare.com
Cc: tpilar@solarflare.com, linux-net-drivers@solarflare.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next] sfc: reduce severity of PIO buffer alloc failures
Date: Wed, 25 Jan 2017 14:44:10 -0500 (EST)	[thread overview]
Message-ID: <20170125.144410.136728977042293227.davem@davemloft.net> (raw)
In-Reply-To: <4bb401da-f76d-38e8-2368-d36edeb4ac44@solarflare.com>

From: Bert Kenward <bkenward@solarflare.com>
Date: Wed, 25 Jan 2017 13:48:17 +0000

> From: Tomáš Pilař <tpilar@solarflare.com>
> 
> PIO buffer allocation can fail for two valid reasons:
>  - we've run out of them (results in -ENOSPC)
>  - the NIC configuration doesn't support them (results in -EPERM)
> Since both these failures are expected netif_err is excessive.
> 
> Signed-off-by: Bert Kenward <bkenward@solarflare.com>

Applied.

      reply	other threads:[~2017-01-25 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 13:48 [PATCH net-next] sfc: reduce severity of PIO buffer alloc failures Bert Kenward
2017-01-25 19:44 ` 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=20170125.144410.136728977042293227.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bkenward@solarflare.com \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=tpilar@solarflare.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