netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@purestorage.com>
To: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Cc: venkat.x.venkatsubra@oracle.com, davem@davemloft.net,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	dledford@redhat.com, Jes.Sorensen@redhat.com,
	rds-devel@oss.oracle.com
Subject: Re: [PATCH] rds_rdma: don't assume infiniband device is PCI
Date: Fri, 6 Jan 2012 09:49:36 -0800	[thread overview]
Message-ID: <CAL1RGDVEqr9XzzcpG6wK49e209JtrhXGayFa5Qnz_NziLinR-g@mail.gmail.com> (raw)
In-Reply-To: <CAL1RGDWOitrKp31RuWLCV3ifUa=CKvZ2qZaRQJMcxdU6_eubww@mail.gmail.com>

On Fri, Jan 6, 2012 at 9:47 AM, Roland Dreier <roland@purestorage.com> wrote:
> Looks great to me:

And BTW if Oracle has some non-published work they should probably just
rebase it on top of this fix.  We should merge this rather than shipping a
kernel with an obvious know crash like this.

 - R.

  reply	other threads:[~2012-01-06 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 22:03 [PATCH] rds_rdma: don't assume infiniband device is PCI Thadeu Lima de Souza Cascardo
2012-01-06 17:47 ` Roland Dreier
2012-01-06 17:49   ` Roland Dreier [this message]
2012-01-13 18:17     ` Thadeu Lima de Souza Cascardo
2012-01-13 18:25       ` David Miller
2012-01-13 18:52         ` Thadeu Lima de Souza Cascardo
2012-01-13 21:12           ` David Miller
2012-01-13 21:21             ` Thadeu Lima de Souza Cascardo
2012-01-13 18:35       ` Roland Dreier
     [not found] <ed54708d-990e-4c8f-8057-50a70f93d3d8@default>
2012-01-05 17:05 ` Thadeu Lima de Souza Cascardo
2012-01-05 18:57   ` David Miller
2012-01-06 15:57   ` Thadeu Lima de Souza Cascardo
2012-01-06 17:43     ` Thadeu Lima de Souza Cascardo
  -- strict thread matches above, loose matches on Subject: below --
2012-01-06 19:27 Venkat Venkatsubra

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=CAL1RGDVEqr9XzzcpG6wK49e209JtrhXGayFa5Qnz_NziLinR-g@mail.gmail.com \
    --to=roland@purestorage.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=cascardo@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=venkat.x.venkatsubra@oracle.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).