Date: Wed, 30 Nov 2016 09:53:58 -0500 (EST)
Message-Id: <20161130.095358.78026433661495653.davem@davemloft.net>
To: maan@tuebingen.mpg.de
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
        torvalds@linux-foundation.org, akpm@linux-foundation.org,
        linux@roeck-us.net, shuah.kh@samsung.com, patches@kernelci.org,
        ben.hutchings@codethink.co.uk, stable@vger.kernel.org,
        edumazet@google.com, alexander.h.duyck@intel.com
Subject: Re: [PATCH 4.4 00/21] 4.4.36-stable review
From: David Miller <davem@davemloft.net>
In-Reply-To: <20161130140438.GB14154@tuebingen.mpg.de>
References: <20161130134619.GA14154@tuebingen.mpg.de>
        <20161130135327.GA1283@kroah.com>
        <20161130140438.GB14154@tuebingen.mpg.de>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 972
Lines: 23

From: Andre Noll <maan@tuebingen.mpg.de>
Date: Wed, 30 Nov 2016 15:04:38 +0100

> On Wed, Nov 30, 14:53, Greg Kroah-Hartman wrote
>> > It fixes a regression introduced in 4.4.34 which makes systems
>> > unbootable for us. We are currently running that patch on top of
>> > 4.4.35 and I can confirm that it fixes the issue.
>> 
>> I wait for networking stable patches to come from the networking
>> maintainer, as he batches them up and runs them through testing before
>> forwarding them on.
>> 
>> That being said, this looks like an "easy" one to take, Davie, any
>> objection to me queueing this up now?
> 
> OK, thanks for the clarification. There is no hurry, I just wanted to
> make sure the patch doesn't get lost.

There is never any ambiguity or guessing for networking patches, you
can always simply check right here to see if a networking patch is
pending to be sent to -stable:

	http://patchwork.ozlabs.org/bundle/davem/stable/?submitter=&state=*&q=&archive=