public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, alsa-devel@alsa-project.org,
	pierre-louis.bossart@linux.intel.com,
	ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
	rander.wang@intel.com, yung-chuan.liao@linux.intel.com
Subject: Re: [PATCH] ASoC: SOF: Intel: hda-dai: fix possible stream_tag leak
Date: Thu, 16 Feb 2023 18:24:52 +0200	[thread overview]
Message-ID: <33fd3541-688d-74b0-cc9d-98bdb0c9e035@linux.intel.com> (raw)
In-Reply-To: <Y+5RjX3cB9gwnvVs@sirena.org.uk>



On 16/02/2023 17:53, Mark Brown wrote:
> On Thu, Feb 16, 2023 at 04:40:54PM +0200, Peter Ujfalusi wrote:
> 
>> is there still time to send this for v6.2?
>> If not, then I will re-send it with stable 6.2 tag.
> 
> In general it's best to just include the relevant Fixes: if
> you're concerned about this...  it's rather late and Takashi was
> looking for early pull requests, I can apply and send but now I
> have to wait for you to tell me the commit it's fixing in case it
> doesn't get pulled in in time which just slows things down :/

OK, I sent v2 with a Complement tag to guide the patch to 6.2 and I will
try to track back the stable kernels and send a clean backport when this
is in mainline.

-- 
Péter

  reply	other threads:[~2023-02-16 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 14:40 [PATCH] ASoC: SOF: Intel: hda-dai: fix possible stream_tag leak Peter Ujfalusi
2023-02-16 15:53 ` Mark Brown
2023-02-16 16:24   ` Péter Ujfalusi [this message]
2023-02-17  1:54 ` Mark Brown

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=33fd3541-688d-74b0-cc9d-98bdb0c9e035@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rander.wang@intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=yung-chuan.liao@linux.intel.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