From: David Miller <davem@davemloft.net>
To: cascardo@linux.vnet.ibm.com
Cc: roland@purestorage.com, venkat.x.venkatsubra@oracle.com,
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, 13 Jan 2012 13:12:48 -0800 (PST) [thread overview]
Message-ID: <20120113.131248.447541680022014759.davem@davemloft.net> (raw)
In-Reply-To: <20120113185258.GB3904@oc1711230544.ibm.com>
From: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Date: Fri, 13 Jan 2012 16:52:58 -0200
> On Fri, Jan 13, 2012 at 10:25:18AM -0800, David Miller wrote:
>> From: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
>> Date: Fri, 13 Jan 2012 16:17:06 -0200
>>
>> > Is this going through your tree? In patchwork, its state is "Not
>> > Applicable".
>>
>> There was an active RDS maintainer, though I haven't seen patches
>> from that person in a while.
>>
>
> Hi, David.
>
> Venkat is the current RDS maintainer and he has Acked the patch.
Not according to patchwork. I don't see him reply at all to the
patch posting and give his explicit "Acked-by: "
next prev parent reply other threads:[~2012-01-13 21:13 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
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 [this message]
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=20120113.131248.447541680022014759.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jes.Sorensen@redhat.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=roland@purestorage.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).