On Tue, 16 Aug 2022 10:15:44 +0200, Cezary Rojewski wrote: > > On 2022-08-15 7:42 PM, Cezary Rojewski wrote: > > A follow up to the recent HDAudio fixes series [1]. Given the recently > > reported regression [2], before the page fault occurring on codec > > shutdown can be fixed, codec construction procedure needs to be updated > > for skylake and sof-intel drivers. Drivers: pci-hda and avs need no > > changes - already making use of snd_hda_codec_device_init(). > > ... > > > Cezary Rojewski (6): > > ASoC: Intel: Skylake: Introduce HDA codec init and exit routines > > ASoC: SOF: Intel: Introduce HDA codec init and exit routines > > ASoC: Intel: Drop hdac_ext usage for codec device creation > > ALSA: hda: Always free codec on the device release > > ALSA: hda: Remove codec init and exit routines > > ALSA: hda: Fix page fault in snd_hda_codec_shutdown() > > > I've received a message yesterday that patches: 1/6, 3/6 and 6/6 were > not delivered to recipient: alsa-devel@xxxxxxxxxxxxxxx. None else is > listed there. lore.kernel.org also shows only four letters (3 + > cover-letter) rather than seven. Given Mark's Ack on patch 3/6 it > makes me believe that indeed just the alsa-devel did not received some > of the messages. > > What should I do in such situation? Is the server admin about to > "recover them from the void" or should I resend the entire series as: > "[RESEND PATCH v2]" as see how it goes this time? I guess the full resubmission would be better. Takashi
