nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"Verma, Vishal L" <vishal.l.verma@intel.com>
Subject: Re: [ndctl PATCH] libndctl: set errno for routines that don't return an error status
Date: Thu, 4 Oct 2018 22:54:57 +0000	[thread overview]
Message-ID: <1dace9aed7cd223fc4e206e69b98b58c947fec17.camel@intel.com> (raw)
In-Reply-To: <20181004223412.17403-1-vishal.l.verma@intel.com>

On Thu, 2018-10-04 at 16:34 -0600, Vishal Verma wrote:
> For routines that return a UINT_MAX or UL{L}ONG_MAX, there isn't a
> way
> to get any information as to what went wrong. Set errno in such
> routines
> so that the callers can get some additional context about the error.

Looks ok, but why EOVERFLOW and not ENOMEM for the out of resource
Linux-nvdimm mailing list

  reply	other threads:[~2018-10-04 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 22:34 Vishal Verma
2018-10-04 22:54 ` Williams, Dan J [this message]
2018-10-04 23:01   ` Verma, Vishal L
2018-10-04 23:11     ` Williams, Dan J
2018-10-04 23:13       ` Verma, Vishal L

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1dace9aed7cd223fc4e206e69b98b58c947fec17.camel@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vishal.l.verma@intel.com \
    --subject='Re: [ndctl PATCH] libndctl: set errno for routines that don'\''t return an error status' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).