[openib-general] [PATCHES] for 2.6.19

[Roland Dreier]

Thanks, I applied all 6 to for-2.6.19 (although I folded 0004 and 0005
into a single patch)

 > Let me know if you'd prefer these in another format (such as inline).

I handled it all myself this time, but in the future it is easier for
me if each patch is inline in a separate email.  A couple of other
things that would also make my life easier:

 - Try to keep authorship information intact -- I assume 0004 and 0005
   were written by James, so I added a "From:" line with his info in
   it to get the write author in git.

 - Have the Subject: of the email be a short description with
   "IB/<area>: " at the beginning, and put the patch description in
   the body.  For example, for patch 0006, I had to munge

Subject: [PATCH] Randomize the starting local comm ID to avoid getting a rejected connection
due to a stale connection after a system reboot or reloading of the ib_cm.

   into

Subject: [PATCH] IB/cm: Randomize starting comm ID

Randomize the starting local comm ID to avoid getting a rejected
connection due to a stale connection after a system reboot or
reloading of the ib_cm.

 - a couple of patches had trailing whitespace, which I had to fix up
   by hand (since I have git set up to error out in that case, as
   maintainers are supposed to).  Adding

[apply]
        whitespace = error-all

   to your git config would help avoid this.

Also, if you want to set up an externally visible git tree somewhere
(I think you could probably get a kernel.org account if you asked),
then I would be glad to just pull from you to get the patches.

 - R.