[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUUnwG2gDa-sCxj+C_pKFROM-zMHAUoX9q8Hurk-sYQYNQ@mail.gmail.com>
Date: Tue, 8 Mar 2016 17:15:13 +0100
From: Sedat Dilek <sedat.dilek@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4.4 00/74] 4.4.5-stable review
On Tue, Mar 8, 2016 at 2:39 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Tue, Mar 08, 2016 at 10:12:13AM +0100, Sedat Dilek wrote:
>> Hi Greg,
>>
>> I tested with my usual setup/config.
>>
>> Looks good so far.
>>
>> Missing some net-ppp-fixes / overlayfs-fixes / userfaultfd-fixes, but
>> I guess you will pick them up in a 6th run of Linux v4.4.y.
>
> I have no idea what these "fixes" are you speak of, my queue is empty,
> there are no known stable patches I haven't applied yet. What exactly
> are you referring to here?
>
> thansk,
>
>
Here we go...
[1] "userfaultfd: don't block on the last VM updates at exit time"
[2] "ppp: release rtnl mutex when interface creation fails"
( I was involved in... Fixes: 58a89ecaca53 ("ppp: fix lockdep splat in
ppp_dev_uninit()" )
[3] "ovl: fix working on distributed fs as lower layer"
BTW, in [1] Linus forgot to add a "CC:stable", how is this handled
when a maintainer forgets this?
Once I read something like "CC:stable # Backport to all applicable
versions". Is that "allowed"?
And yes, netdev has its own rules, so - no comments on this.
- Sedat -
[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=39680f50ae54cbbb6e72ac38b8329dd3eb9105f4
[2] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6faac63a6986f29ef39827f460edd3a5ba64ad5c
[3] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b5891cfab08fe3144a616e8e734df7749fb3b7d0
Powered by blists - more mailing lists