From: Kalle Valo <kvalo@adurom.com>
To: Dan Carpenter <error27@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] wl1251: wl12xx_get_platform_data() returns an ERR_PTR
Date: Sat, 18 Dec 2010 09:12:10 +0000 [thread overview]
Message-ID: <8762urigwl.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20101218085210.GO1639@bicker> (Dan Carpenter's message of "Sat\, 18 Dec 2010 11\:52\:10 +0300")
Dan Carpenter <error27@gmail.com> writes:
> wl12xx_get_platform_data() returns an ERR_PTR on failure and it never
> returns a NULL.
Yes, that's true. Good that you found this.
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Acked-by: Kalle Valo <kvalo@adurom.com>
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@adurom.com>
To: Dan Carpenter <error27@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] wl1251: wl12xx_get_platform_data() returns an ERR_PTR
Date: Sat, 18 Dec 2010 11:12:10 +0200 [thread overview]
Message-ID: <8762urigwl.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20101218085210.GO1639@bicker> (Dan Carpenter's message of "Sat\, 18 Dec 2010 11\:52\:10 +0300")
Dan Carpenter <error27@gmail.com> writes:
> wl12xx_get_platform_data() returns an ERR_PTR on failure and it never
> returns a NULL.
Yes, that's true. Good that you found this.
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Acked-by: Kalle Valo <kvalo@adurom.com>
--
Kalle Valo
next prev parent reply other threads:[~2010-12-18 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 8:52 [patch -next] wl1251: wl12xx_get_platform_data() returns an ERR_PTR Dan Carpenter
2010-12-18 8:52 ` Dan Carpenter
2010-12-18 9:12 ` Kalle Valo [this message]
2010-12-18 9:12 ` Kalle Valo
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=8762urigwl.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.