On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
> On 02/02/2017 01:23 PM, Greg KH wrote:
> > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> >> Hello,
> >>
> >> Please consider reverting commit
> >> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
> > What release can I remove it from?
> >
> > It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
> > reverted in Linus's tree already?
> >
> > totally confused.
> >
> > greg k-h
>
> Sorry, commit 4c63c2454eff996c5e27991221106eb511f7db38 was introduced in
> mainline in v4.7-rc1. The request should be only for kernels newer than
> 4.7-rc1, so 4.9 and 4.10.
>
> I assume it will come down to 4.9 once reverted in mainline.
Let me know when it is reverted, and what that revert commit is please.
On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote: c5e27991221106e b511f7db38 in the next v4.x.y release. c5e27991221106e b511f7db38 was introduced in
> On 02/02/2017 01:23 PM, Greg KH wrote:
> > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> >> Hello,
> >>
> >> Please consider reverting commit
> >> 4c63c2454eff996
> > What release can I remove it from?
> >
> > It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
> > reverted in Linus's tree already?
> >
> > totally confused.
> >
> > greg k-h
>
> Sorry, commit 4c63c2454eff996
> mainline in v4.7-rc1. The request should be only for kernels newer than
> 4.7-rc1, so 4.9 and 4.10.
>
> I assume it will come down to 4.9 once reverted in mainline.
Let me know when it is reverted, and what that revert commit is please.
thanks,
greg k-h