From: Cezary Rojewski <cezary.rojewski@intel.com>
To: <alsa-devel@alsa-project.org>, <broonie@kernel.org>, <tiwai@suse.com>
Cc: hdegoede@redhat.com, amadeuszx.slawinski@linux.intel.com,
pierre-louis.bossart@linux.intel.com,
kai.vehmanen@linux.intel.com
Subject: Re: [RESEND PATCH v2 0/6] ALSA: hda: Unify codec construction
Date: Tue, 16 Aug 2022 13:30:51 +0200 [thread overview]
Message-ID: <7fdabdc0-646a-2bae-902b-777837b2979e@intel.com> (raw)
In-Reply-To: <20220816111727.3218543-1-cezary.rojewski@intel.com>
On 2022-08-16 1:17 PM, Cezary Rojewski wrote:
...
> 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()
All of these landed on lore.kernel.org without problems now.
The only thing I can think of that could offended the server is the
incorrect email address that I had appended to hsw-bdw related series
[1] which I'd sent before the unify-hda-ctor v2 one. Kai's email was
provided twice there - by mistake - and the second copy is missing 'm'
in '@linux.intel.com'. Perhaps these topics are not connected but it's
the only offending action that I've managed to find.
Regards,
Czarek
next prev parent reply other threads:[~2022-08-16 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 11:17 [RESEND PATCH v2 0/6] ALSA: hda: Unify codec construction Cezary Rojewski
2022-08-16 11:17 ` [RESEND PATCH v2 1/6] ASoC: Intel: Skylake: Introduce HDA codec init and exit routines Cezary Rojewski
2022-08-16 11:23 ` Mark Brown
2022-08-16 11:17 ` [RESEND PATCH v2 2/6] ASoC: SOF: Intel: " Cezary Rojewski
2022-08-16 11:17 ` [RESEND PATCH v2 3/6] ASoC: Intel: Drop hdac_ext usage for codec device creation Cezary Rojewski
2022-08-16 11:17 ` [RESEND PATCH v2 4/6] ALSA: hda: Always free codec on the device release Cezary Rojewski
2022-08-16 11:17 ` [RESEND PATCH v2 5/6] ALSA: hda: Remove codec init and exit routines Cezary Rojewski
2022-08-16 11:17 ` [RESEND PATCH v2 6/6] ALSA: hda: Fix page fault in snd_hda_codec_shutdown() Cezary Rojewski
2022-08-16 11:30 ` Cezary Rojewski [this message]
2022-08-18 7:52 ` [RESEND PATCH v2 0/6] ALSA: hda: Unify codec construction Takashi Iwai
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=7fdabdc0-646a-2bae-902b-777837b2979e@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.