Re: mlx4 problems with 4.2-rc8

[Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

On 09/01/2015 05:50 AM, Or Gerlitz wrote:
> On Tue, Sep 1, 2015 at 11:42 AM, Matan Barak <matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> wrote:
> 
>> If I recall, this code was sent through linux-net mailing list. So
>> it's possible the different branches weren't rebased, isn't it?
> 
> but the code was merged for 4.2-rc1 -- so Doug, this means that when
> you did the 4.2-rc work you haven't rebased to 4.2-rc1 -- if this is
> indeed the case,
> such practice is problematic, agree?

That depends.  Early on in the rc series, I don't rebase for testing.
Later on in the rc series, I do.  However, that's all moot because it
isn't why I didn't see this in the 4.2 rc series.  I only have one
machine with > 32 CPUs, and it's intended to be a highly reliable/stable
machine.  I don't always use it for testing new kernels.  In this
particular case, I needed to move it from a RHEL kernel to an upstream
kernel to isolate a different issue, and hence I ran across this
problem.  My more common test machines would have never seen the issue I
reported.


-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]