Hi,
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, April 18, 2014 11:40 AM
>
> On Fri, Apr 18, 2014 at 03:00:21AM +, Zheng, Lv wrote:
> > Hi, Greg
> >
> > > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > > Sent: Friday, April 18, 2014 10:44 AM
> > >
> > > On Fri,
Hi,
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Friday, April 18, 2014 11:40 AM
On Fri, Apr 18, 2014 at 03:00:21AM +, Zheng, Lv wrote:
Hi, Greg
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Friday, April 18, 2014 10:44 AM
On Fri, Apr 18, 2014 at
On Fri, Apr 18, 2014 at 03:00:21AM +, Zheng, Lv wrote:
> Hi, Greg
>
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Friday, April 18, 2014 10:44 AM
> >
> > On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > > Note that this patch is only used for stable kernels,
Hi,
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, April 18, 2014 10:44 AM
>
> On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > Note that this patch is only used for stable kernels, upstream kernels
> > will have this problem fixed in ACPICA 201303-04 release.
Hi, Greg
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, April 18, 2014 10:44 AM
>
> On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > Note that this patch is only used for stable kernels, upstream kernels
> > will have this problem fixed in ACPICA 201303-04
On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> Note that this patch is only used for stable kernels, upstream kernels
> will have this problem fixed in ACPICA 201303-04 release. So upstream
> kernels shouldn't merge this commit.
What kernel commit fixed this issue in "upstream"?
>
Hi, Stable reviewers
This patch is not included in any upstream kernel, so it might not follow the
stable rule.
If you think you need more information, please ignore this message.
This urgent fix is sent here for people who are monitoring stable and seeking
for this fix.
Thanks and best
Hi, Stable reviewers
This patch is not included in any upstream kernel, so it might not follow the
stable rule.
If you think you need more information, please ignore this message.
This urgent fix is sent here for people who are monitoring stable and seeking
for this fix.
Thanks and best
On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
Note that this patch is only used for stable kernels, upstream kernels
will have this problem fixed in ACPICA 201303-04 release. So upstream
kernels shouldn't merge this commit.
What kernel commit fixed this issue in upstream?
It is
Hi, Greg
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Friday, April 18, 2014 10:44 AM
On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
Note that this patch is only used for stable kernels, upstream kernels
will have this problem fixed in ACPICA 201303-04 release. So
Hi,
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Friday, April 18, 2014 10:44 AM
On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
Note that this patch is only used for stable kernels, upstream kernels
will have this problem fixed in ACPICA 201303-04 release. So
On Fri, Apr 18, 2014 at 03:00:21AM +, Zheng, Lv wrote:
Hi, Greg
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Friday, April 18, 2014 10:44 AM
On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
Note that this patch is only used for stable kernels, upstream
12 matches
Mail list logo