On 12-10-08 09:55 PM, Ben Hutchings wrote: > On Mon, 2012-10-08 at 18:07 -0700, Jonathan Nieder wrote: >> From: Seth Heasley <seth.heas...@intel.com> >> Date: Wed, 20 Apr 2011 10:59:57 -0700 >> >> commit d2edeb7c6f1dada8ca7d5c23e42d604e92ae0c76 upstream. >> >> This patch adds the HD Audio Controller DeviceIDs for the Intel Panther >> Point PCH. >> >> [jn: backported for 2.6.32.y by Ana Guerrero] >> >> Signed-off-by: Seth Heasley <seth.heas...@intel.com> >> Signed-off-by: Takashi Iwai <ti...@suse.de> >> Tested-by: Ana Guerrero <a...@debian.org> # EliteBook 8570w >> Signed-off-by: Jonathan Nieder <jrnie...@gmail.com> >> --- >> Hi Willy and Paul, >> >> Please consider >> >> d2edeb7c6f1d ALSA: hda - ALSA HD Audio patch for Intel Panther Point >> DeviceIDs >> >> for application to the 2.6.32.y and 2.6.34.y trees. >> >> It does what it says on the cover. The patch was merged in the 3.0 >> cycle, so newer stable kernels don't need it. Backported and >> tested[1] against Debian's 2.6.32.y-based kernel by Ana (cc-ed) -- >> thanks! >> >> Thoughts of all kinds welcome, as always. > [...] > > I queued up a whole series of device ID updates for Debian stable, as > they didn't obviously depend on other changes: > > cea310e ALSA: hda_intel: ALSA HD Audio patch for Intel Patsburg DeviceIDs > e35d4b1 ALSA: hda: add Vortex86MX PCI ids > 0f0714c ALSA: hda - Add support for VMware controller > d2edeb7 ALSA: hda - ALSA HD Audio patch for Intel Panther Point DeviceIDs
I found that d2edeb7c6f depends (only trivially, on context) on b686453543f, which makes a blanket class for intel IDs so that "...the driver will work with any new control chips in future." In that respect, I guess it too (b68645) is in the same class as the other "add more IDs" patches? Paul. -- > > (They can be cherry-picked cleanly in the above order.) But if I've > missed some post-2.6.32 dependencies then I would like to know. > > Ben. > -- 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/
