From: Roland Dreier <rdreier@cisco.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rdma@vger.kernel.org, infinipath@qlogic.com,
Ralph Campbell <ralph.campbell@qlogic.com>
Subject: Re: infiniband BKL leftovers
Date: Sun, 11 Oct 2009 12:27:42 -0700 [thread overview]
Message-ID: <ada8wfhivdd.fsf@cisco.com> (raw)
In-Reply-To: <adad44tj090.fsf@cisco.com> (Roland Dreier's message of "Sun, 11 Oct 2009 10:42:19 -0700")
[Adding Ralph's direct email]
And the address in MAINTAINERS of infinipath@qlogic.com appears to be
bouncing... so I think it's pretty safe to say that Qlogic doesn't care
too much about the ipath driver any more.
- R.
next prev parent reply other threads:[~2009-10-11 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 18:37 infiniband BKL leftovers Thomas Gleixner
2009-10-11 17:42 ` Roland Dreier
2009-10-11 19:27 ` Roland Dreier [this message]
2009-10-11 19:52 ` Thomas Gleixner
2009-10-14 15:51 ` [tip:bkl/drivers] inifiband: Remove BKL from ipath_open() tip-bot for Thomas Gleixner
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=ada8wfhivdd.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=infinipath@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ralph.campbell@qlogic.com \
--cc=tglx@linutronix.de \
/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