Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: alsa-devel@alsa-project.org, kai.vehmanen@linux.intel.com,
	pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
	hdegoede@redhat.com, broonie@kernel.org,
	amadeuszx.slawinski@linux.intel.com
Subject: Re: [PATCH v2 0/6] ALSA: hda: Unify codec construction
Date: Tue, 16 Aug 2022 11:59:49 +0200	[thread overview]
Message-ID: <87tu6cy0dm.wl-tiwai@suse.de> (raw)
In-Reply-To: <e8e9eb65-3095-ac5a-ce96-55eaa34ef895@intel.com>

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@alsa-projet.org. 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

  reply	other threads:[~2022-08-16 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 17:42 [PATCH v2 0/6] ALSA: hda: Unify codec construction Cezary Rojewski
2022-08-15 17:42 ` [PATCH v2 2/6] ASoC: SOF: Intel: Introduce HDA codec init and exit routines Cezary Rojewski
2022-08-15 22:14   ` Mark Brown
2022-08-15 17:42 ` [PATCH v2 4/6] ALSA: hda: Always free codec on the device release Cezary Rojewski
2022-08-15 17:42 ` [PATCH v2 5/6] ALSA: hda: Remove codec init and exit routines Cezary Rojewski
     [not found] ` <20220815174227.3071323-4-cezary.rojewski@intel.com>
2022-08-15 22:15   ` [PATCH v2 3/6] ASoC: Intel: Drop hdac_ext usage for codec device creation Mark Brown
2022-08-16  8:15 ` [PATCH v2 0/6] ALSA: hda: Unify codec construction Cezary Rojewski
2022-08-16  9:59   ` Takashi Iwai [this message]
2022-08-16 10:08     ` Cezary Rojewski
2022-08-16 10:30       ` Mark Brown
2022-08-16 10:33         ` Takashi Iwai
2022-08-16 12:35           ` Jaroslav Kysela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tu6cy0dm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox