[openib-general] RE: [PATCH] osm: osm_vendor_umad to provide port state

[Hal Rosenstock]

Hi Eitan,
 
>I hope you will be able to collect valuable inputs to the OpenSM
TODO.

I hope so too (but there already is more than enough to do here).
 
> Also Yael has posted the branch with the merge of the 1.8.0 to the
> current trunk. 
 
Yes, I saw this.
 
> It might be worthwhile to try merging it in before any
> changes in the main trunk. 
 
The only changes would be your 3 outstanding patches.
 
> I know the diff file to review will be huge,
> and cross files this is why we could not do it in patches. The changes
> are considerably big as the main is 1.6.1 + some 1.7.0 and the branch is
> 1.8.0. 
 
I think this can be done in steps as I had described earlier. That is the process I 
will use to merge this to the trunk.
 
> Yael spent two weeks on this merge.
 
I think it was longer. Thanks to Yael for getting this done. I'm sure OpenSM is now 
much better for it. It is a high priority item for me to get this back to the trunk but just as it took time 
to do the merge, I expect it to take some time to put it back on the trunk. You will see postings on questions and
progress on this on the list.
 
-- Hal

 

________________________________

From: Eitan Zahavi [mailto:eitan at mellanox.co.il]
Sent: Mon 8/22/2005 9:18 AM
To: Hal Rosenstock
Cc: OPENIB GENERAL
Subject: Re: [PATCH] osm: osm_vendor_umad to provide port state



Hal Rosenstock wrote:
> I will deal with the osm_vendor_umad patches later in the week upon
> return from the OpenIB workshop.
Thanks I will be waiting patiently. I wish I could come to the workshop
too. I hope you will be able to collect valuable inputs to the OpenSM
TODO.
> I believe there are 3 patches currently
> outstanding.
The patches not yet added are:
osm: osm_vendor_umad to provide port state
osm: osm_vendor_umad registers to all SubnMgt methods
osm: osm_vendor_umad osm_vendor_get_all_port_attr bug

Also Yael has posted the branch with the merge of the 1.8.0 to the
current trunk. It might be worthwhile to try merging it in before any
changes in the main trunk. I know the diff file to review will be huge,
and cross files this is why we could not do it in patches. The changes
are considerably big as the main is 1.6.1 + some 1.7.0 and the branch is
1.8.0. Yael spent two weeks on this merge.