Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>, "Saarinen, Jani" <jani.saarinen@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [Intel-xe] [PATCH 11/14] ALSA: hda/intel: Move snd_hdac_i915_init to before probe_work.
Date: Tue, 14 Nov 2023 19:24:51 +0200	[thread overview]
Message-ID: <874jhos0ws.fsf@intel.com> (raw)
In-Reply-To: <87jzqkp99j.wl-tiwai@suse.de>

On Tue, 14 Nov 2023, Takashi Iwai <tiwai@suse.de> wrote:
> (Also thought that drm-tip or whatever tree also drags the recent
> changes from sound.git tree for relevant part.)

We've dropped the sound branches from drm-tip, mostly because they were
repeatedly rebased on Linus' master (as opposed to tags) during the
merge window.


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2023-11-14 17:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231002193847.7134-1-maarten.lankhorst@linux.intel.com>
     [not found] ` <20231002193847.7134-11-maarten.lankhorst@linux.intel.com>
2023-11-14 11:06   ` [Intel-gfx] [Intel-xe] [PATCH 11/14] ALSA: hda/intel: Move snd_hdac_i915_init to before probe_work Ville Syrjälä
2023-11-14 12:35     ` Jani Nikula
2023-11-14 13:29       ` Maarten Lankhorst
2023-11-14 13:31         ` Saarinen, Jani
2023-11-14 16:52           ` Takashi Iwai
2023-11-14 17:24             ` Jani Nikula [this message]
2023-11-15  8:15             ` Kai Vehmanen
2023-11-14 13:39       ` Ville Syrjälä
2023-11-14 14:39         ` Maarten Lankhorst
2023-11-14 15:50           ` Takashi Iwai
2023-11-14 15:52             ` Maarten Lankhorst
2023-11-14 15:09     ` 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=874jhos0ws.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=suresh.kumar.kurmi@intel.com \
    --cc=tiwai@suse.de \
    /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