Re: Linux 3.8-rc1 (mei driver BROKEN)

2012-12-27 Thread Greg Kroah-Hartman
On Fri, Dec 28, 2012 at 02:04:23AM +0100, Sedat Dilek wrote:
> Hi Linus,
> 
> I am not sure if Greg is on holidays as his char-misc GIT tree didn't
> get updated the last days.

Yes, I'm supposed to be on vacation until the 7th.

> The MEI driver causes here a serious regression requiring a hard cold
> start of the machine I am working on.
> A fix "mei: fix mismatch in mutex unlock-lock in mei_amthif_read()"
> was already sent to LKML [1] and fixes the issue for me.
> 
> Can you push that a bit?

These patches are in my "to-apply" queue, which I will get to Linus in
time for 3.8-final, so there's no rush on your end needed.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 3.8-rc1 (mei driver BROKEN)

2012-12-27 Thread Sedat Dilek
Hi Linus,

I am not sure if Greg is on holidays as his char-misc GIT tree didn't
get updated the last days.

The MEI driver causes here a serious regression requiring a hard cold
start of the machine I am working on.
A fix "mei: fix mismatch in mutex unlock-lock in mei_amthif_read()"
was already sent to LKML [1] and fixes the issue for me.

Can you push that a bit?
Feel free to add any credits.

Regards,
- Sedat -

[1] https://patchwork.kernel.org/patch/1904801/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 3.8-rc1 (mei driver BROKEN)

2012-12-27 Thread Sedat Dilek
Hi Linus,

I am not sure if Greg is on holidays as his char-misc GIT tree didn't
get updated the last days.

The MEI driver causes here a serious regression requiring a hard cold
start of the machine I am working on.
A fix mei: fix mismatch in mutex unlock-lock in mei_amthif_read()
was already sent to LKML [1] and fixes the issue for me.

Can you push that a bit?
Feel free to add any credits.

Regards,
- Sedat -

[1] https://patchwork.kernel.org/patch/1904801/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 3.8-rc1 (mei driver BROKEN)

2012-12-27 Thread Greg Kroah-Hartman
On Fri, Dec 28, 2012 at 02:04:23AM +0100, Sedat Dilek wrote:
 Hi Linus,
 
 I am not sure if Greg is on holidays as his char-misc GIT tree didn't
 get updated the last days.

Yes, I'm supposed to be on vacation until the 7th.

 The MEI driver causes here a serious regression requiring a hard cold
 start of the machine I am working on.
 A fix mei: fix mismatch in mutex unlock-lock in mei_amthif_read()
 was already sent to LKML [1] and fixes the issue for me.
 
 Can you push that a bit?

These patches are in my to-apply queue, which I will get to Linus in
time for 3.8-final, so there's no rush on your end needed.

thanks,

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/