Re: [PATCH 0/29v2] InfiniBand core update

2005-07-12 Thread Hal Rosenstock
On Tue, 2005-07-12 at 18:38, Andrew Morton wrote: > OK, well the timing of a merge is mainly up to you guys, especially as the > subsystem is pretty raw and you're the only people who use it ;) > > Two things from a quick scan: > > a) In many places the patch does > > if (p) >

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-12 Thread Andrew Morton
Hal Rosenstock <[EMAIL PROTECTED]> wrote: > > On Mon, 2005-07-11 at 23:11, Andrew Morton wrote: > > Well I was asking. Do you guys think that this material is appropriate to > > and safe enough for 2.6.13? > > I used your versions of the patches (Tom's ucm one is needed and you > added that). I a

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-12 Thread Hal Rosenstock
On Mon, 2005-07-11 at 23:11, Andrew Morton wrote: > Well I was asking. Do you guys think that this material is appropriate to > and safe enough for 2.6.13? I used your versions of the patches (Tom's ucm one is needed and you added that). I also back ported the trailing whitespace elimination chan

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-12 Thread Hal Rosenstock
On Mon, 2005-07-11 at 23:11, Andrew Morton wrote: > Well I was asking. Do you guys think that this material is appropriate to > and safe enough for 2.6.13? We think so. > What are "user CM" and "kernel CM"? CM is the InfiniBand Communications Manager. It is (primarily) responsible for setting u

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-12 Thread Hal Rosenstock
On Mon, 2005-07-11 at 23:12, David S. Miller wrote: > Please acknowledge that you understand how inappropriate > and problem causing your huge patch bomb was today to this > mailing list. > > It is nearly 8 hours later, and vger.kernel.org is still > trying mightily to spit out all of your patches

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-11 Thread David S. Miller
Please acknowledge that you understand how inappropriate and problem causing your huge patch bomb was today to this mailing list. It is nearly 8 hours later, and vger.kernel.org is still trying mightily to spit out all of your patches to the 5000+ people subscribed to linux-kernel. There is abou

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-11 Thread Andrew Morton
Hal Rosenstock <[EMAIL PROTECTED]> wrote: > > > I'll tentatively consider this material to be not-for-2.6.13? > > Presuming that "this material" refers to the patch to add the kernel CM > implementation, if kernel CM does not make 2.6.13, then user CM should > not either as it is dependent on i

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-11 Thread Hal Rosenstock
On Mon, 2005-07-11 at 20:05, Andrew Morton wrote: > Hal Rosenstock <[EMAIL PROTECTED]> wrote: > > > > This is version 2 of a patch series to get the Infiniband core up to > > date. > > Well that was interesting. > > - All the patches had mangled headers: > > -- linux-2.6.13-rc2-mm1-16/... > +++

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-11 Thread David S. Miller
NO No more huge patch bombs to linux-kernel@vger.kernel.org people! Condense your changes into more manageable pieces or only submit smaller groups of changes at a time. You people doing this are absolutely killing vger.kernel.org. Every patch you post has to go to 5000+ subscribers, so ple

Re: [PATCH 0/29v2] InfiniBand core update

2005-07-11 Thread Andrew Morton
Hal Rosenstock <[EMAIL PROTECTED]> wrote: > > This is version 2 of a patch series to get the Infiniband core up to > date. Well that was interesting. - All the patches had mangled headers: -- linux-2.6.13-rc2-mm1-16/... +++ linux-2.6.13-rc2-mm1-17/... instead of --- linux-2.6.13-rc2-mm1-16/.