Re: [PATCH 3.4.x 0/1] missing patches for 3.4.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2014/4/10 10:42, Li Zefan wrote:
> On 2014/4/10 10:30, Weng Meiling wrote:
>> On 2014/4/10 7:37, Greg KH wrote:
>>> On Wed, Mar 12, 2014 at 05:16:47PM +0800, Weng Meiling wrote:
>>>> Hi Greg,
>>>>
>>>> We've started to analize the list of upstream commits that have been
>>>> backported to 3.2 but missing from 3.4.
>>>>
>>>> For the 13 commits that I've analized,
>>>> - 3 commits have no stable tag. I've found out why they were backported to 3.2.x,
>>>>   and I'm sure they shoud be applied to 3.4.x.
>>>> - 7 commits were marked for stable but can't be applied cleanly to 3.4.
>>>> - 3 commits about new feature for CX2075X codec ID support.
>>>>
>>>> There is 1 other commit that needs trivial context adjustments. I'll send out
>>>> the backport. Please apply this first, because patches about internal mic rely
>>>> on it.
>>>> 	
>>>> Please cherry-pick those commits from 3.2.x:
>>>> d2f11b9e8718 ALSA: HDA: Add inverted internal mic quirk for Lenovo S205
>>>> 7737238648b5 ALSA: hda - Add inverted internal mic quirk for Lenovo IdeaPad U310
>>>> 810352f7bc7e ALSA: hda - Fix oops caused by recent commit "Fix internal mic for Lenovo Ideapad U300s"
>>>> d59c4a70d307 ALSA: hda - Add stereo-dmic fixup for Acer Aspire One 522
>>>> 7f778c1b063b ALSA: hda - Always turn on pins for HDMI/DP
>>>> 5b7d898a1904 Revert "ALSA: hda - Shut up pins at power-saving mode with Conexnat codecs"
>>>> 91abcd9460c3 ALSA: hda - Add Conexant CX20751/2/3/4 codec support
>>>> fc9c1a6fcab3 ALSA: hda/conexant - Correct vendor IDs for new codecs
>>>> 08a43c183143 ALSA: hda - Add Conexant CX20755/20756/20757 codec IDs
>>>> d027778a1cf8 ALSA: hda - Fix non-snoop page handling
>>>> bc32ef0a6d6a ALSA: aloop: Fix Oops while PM resume
>>>> 40de8047654d ALSA: usb: Add quirk for 192KHz recording on E-Mu devices
>>>
>>> a bunch of these did not apply at all, and even with some that did, they
>>> broke the build :(
>>>
>>> So, I've applied some of these, and fixed up the build, but please be
>>> much more careful in the future, it's obvious something went wrong
>>> here...
>>>
>> I'm sorry for this. I'll find out what's wrong and send another version with
>> the left patches.
>>
> 
> probably because they conflict with some patches that went into 3.4.x after
> you sent out this email.
> 
> I was able to apply them successfully when I was doing the review.
> 
> 
yeah, it maybe. :)
I'll do the backport on the lastest 3.4.x tree again for the left patches and resent them.

Thanks!
Weng Meiling

--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]