From: Divy Le Ray <divy@chelsio.com>
To: Divy Le Ray <divy@chelsio.com>
Cc: Steve Wise <swise@opengridcomputing.com>,
Roland Dreier <rdreier@cisco.com>,
netdev@vger.kernel.org, openib-general@openib.org,
linux-kernel@vger.kernel.org, Felix Marti <felix@chelsio.com>
Subject: Re: [PATCH v3 00/13] 2.6.20 Chelsio T3 RDMA Driver
Date: Mon, 11 Dec 2006 11:49:53 -0800 [thread overview]
Message-ID: <457DB661.6060102@chelsio.com> (raw)
In-Reply-To: <457DB08C.8070709@chelsio.com>
Divy Le Ray wrote:
> Steve Wise wrote:
>> On Sun, 2006-12-10 at 20:02 -0800, Roland Dreier wrote:
>>
>>> I haven't seen any evidence of the corresponding ethernet NIC driver
>>> being merged for 2.6.20 (which is a prerequisite, right).
>>>
>>> What's the status of that?
>>>
>>>
>>
>> It is on its third or fourth round of review. The last driver posted on
>> 12/7, was merged up to linus's latest tree probably as of 12/7. I know
>> the comments set it was against 2.6.19, but it was really linus's
>> latest.
>>
>> Divy, can you expand on this?
>>
> Steve, the patch for the Chelsio T3 driver was postered against
> Linus'tree indeed.
>
> -bash-3.00$ cat .git/refs/heads/origin
> 0215ffb08ce99e2bb59eca114a99499a4d06e704
I meant
-bash-3.00$ cat .git/refs/heads/master
9eba2b0ba067ce9745e575e5ea2e97a5d7d61bef
>
> It incorporated Stephen's feedback.
> The comments I received since then concern minor coding style glitches.
> I will fix them, the driver functionality should remain unchanged
> however.
>
> Cheers,
> Divy
>
>
>>
>> Steve.
>>
>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2006-12-11 19:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 22:32 [PATCH v3 00/13] 2.6.20 Chelsio T3 RDMA Driver Steve Wise
2006-12-10 22:33 ` [PATCH v3 01/13] Linux RDMA Core Changes Steve Wise
2006-12-10 22:33 ` [PATCH v3 02/13] Device Discovery and ULLD Linkage Steve Wise
2006-12-10 22:34 ` [PATCH v3 03/13] Provider Methods and Data Structures Steve Wise
2006-12-10 22:34 ` [PATCH v3 04/13] Connection Manager Steve Wise
2006-12-10 22:35 ` [PATCH v3 05/13] Queue Pairs Steve Wise
2006-12-10 22:35 ` Steve Wise
2006-12-10 22:35 ` [PATCH v3 06/13] Completion Queues Steve Wise
2006-12-10 22:36 ` [PATCH v3 07/13] Async Event Handler Steve Wise
2006-12-10 22:36 ` [PATCH v3 08/13] Memory Registration Steve Wise
2006-12-10 22:37 ` [PATCH v3 09/13] Core WQE/CQE Types Steve Wise
2006-12-10 22:37 ` [PATCH v3 10/13] Core HAL Steve Wise
2006-12-10 22:37 ` Steve Wise
2006-12-10 22:38 ` [PATCH v3 11/13] Core Resource Allocation Steve Wise
2006-12-10 22:38 ` Steve Wise
2006-12-10 22:38 ` [PATCH v3 12/13] Core Debug functions Steve Wise
2006-12-10 22:38 ` Steve Wise
2006-12-10 22:39 ` [PATCH v3 13/13] Kconfig/Makefile Steve Wise
2006-12-10 22:56 ` Randy Dunlap
2006-12-10 23:04 ` Steve WIse
2006-12-11 5:02 ` Roland Dreier
2006-12-11 4:02 ` [PATCH v3 00/13] 2.6.20 Chelsio T3 RDMA Driver Roland Dreier
2006-12-11 15:36 ` Steve Wise
2006-12-11 19:25 ` Divy Le Ray
2006-12-11 19:49 ` Divy Le Ray [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=457DB661.6060102@chelsio.com \
--to=divy@chelsio.com \
--cc=felix@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
--cc=swise@opengridcomputing.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.