netdev - Re: [PATCH 04/39] wimax: internal API for the kernel space WiMAX stack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200812041122.13320.inaky@linux.intel.com>
Date:	Thu, 4 Dec 2008 11:22:13 -0800
From:	Inaky Perez-Gonzalez <inaky@...ux.intel.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 04/39] wimax: internal API for the kernel space WiMAX stack

On Thursday 04 December 2008, Johannes Berg wrote:
> On Tue, 2008-12-02 at 18:07 -0800, Inaky Perez-Gonzalez wrote:
> > > > +static inline __must_check
> > > > +int wimax_dev_is_ready(struct wimax_dev *wimax_dev)
> > > > +{
> > > > +	if (wimax_dev->state == __WIMAX_ST_NULL)
> > > > +		return -EINVAL;	/* Device is not even registered! */
> > > > +	if (wimax_dev->state == WIMAX_ST_DOWN)
> > > > +		return -ENOMEDIUM;
> > >
> > > ENOLINK seems more appropriate?
> >
> > Well, this means there is no medium on which to try to establish a
> > link. It doesn't really matter.
> >
> > Is it used mainly for storage applications?
>
> Yes, I think so.

Ack, I'll switch it to -ENOLINK.

Thanks,

-- 
Inaky
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html