From: Roland Dreier <rdreier@cisco.com>
To: akpm@linux-foundation.org
Cc: jeff@garzik.org, netdev@vger.kernel.org, 12o3l@tiscali.nl,
fenkes@de.ibm.com, hnguyen@de.ibm.com, paulus@samba.org,
stefan.roscher@de.ibm.com
Subject: Re: [patch 05/11] ehca: ret is unsigned, ibmebus_request_irq() negative return ignored in hca_create_eq()
Date: Wed, 14 May 2008 16:37:43 -0700 [thread overview]
Message-ID: <ada4p90ihiw.fsf@cisco.com> (raw)
In-Reply-To: <200805142320.m4ENKCQl026623@imap1.linux-foundation.org> (akpm@linux-foundation.org's message of "Wed, 14 May 2008 16:20:12 -0700")
This is a drivers/infiniband patch, not a drivers/net patch.
I believe this is already fixed upstream by 7df109d9 ("IB/ehca: handle
negative return value from ibmebus_request_irq() properly").
- R.
prev parent reply other threads:[~2008-05-14 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:20 [patch 05/11] ehca: ret is unsigned, ibmebus_request_irq() negative return ignored in hca_create_eq() akpm
2008-05-14 23:37 ` Roland Dreier [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=ada4p90ihiw.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=12o3l@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=fenkes@de.ibm.com \
--cc=hnguyen@de.ibm.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=stefan.roscher@de.ibm.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;
as well as URLs for NNTP newsgroup(s).