From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: fprintf stderr in libibverbs
Date: Wed, 28 Oct 2009 10:51:22 -0700 [thread overview]
Message-ID: <adazl7bs8yt.fsf@cisco.com> (raw)
In-Reply-To: <20091028054232.GA1966-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> (Jason Gunthorpe's message of "Tue, 27 Oct 2009 23:42:32 -0600")
> My main goal would be to remove prints from the library in common
> cases like no IB drivers loaded, no devices present, or no
> permissions. I have an app where the prints are inconvient.
>
> What I was thinking was to return these cases via errno (ENOSYS,
> ENODEV, EPERM) in ibv_get_device_list. Do you think that is OK?
Yes, that makes sense I guess.
> int ibv_get_device_list_ex(struct ibv_device ***devices,int *num_devices,
> const char **warning_msg);
Are there that many cases where the output is important enough and
likely enough that it's worth a new API to get it out when stderr
doesn't suffice?
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-28 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 5:42 fprintf stderr in libibverbs Jason Gunthorpe
[not found] ` <20091028054232.GA1966-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-10-28 17:51 ` Roland Dreier [this message]
[not found] ` <adazl7bs8yt.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2009-10-28 21:05 ` Jason Gunthorpe
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=adazl7bs8yt.fsf@cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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