Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     alsa-devel@alsa-project.org,
        Daniel Baluta <daniel.baluta@oss.nxp.com>
Cc:     ranjani.sridharan@linux.intel.com, yung-chuan.liao@linux.intel.com,
        pierre-louis.bossart@linux.intel.com,
        peter.ujfalusi@linux.intel.com,
        Daniel Baluta <daniel.baluta@nxp.com>, lgirdwood@gmail.com,
        kernel test robot <lkp@intel.com>,
        linux-kernel@vger.kernel.org, kai.vehmanen@linux.intel.com
In-Reply-To: <20220822174937.254873-1-daniel.baluta@oss.nxp.com>
References: <20220822174937.254873-1-daniel.baluta@oss.nxp.com>
Subject: Re: [PATCH] ASoC: SOF: compress: Remove dai_posn variable
Message-Id: <166128059751.1031684.6362088791172112373.b4-ty@kernel.org>
Date:   Tue, 23 Aug 2022 19:49:57 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 22 Aug 2022 20:49:37 +0300, Daniel Baluta wrote:
> From: Daniel Baluta <daniel.baluta@nxp.com>
> 
> dai_posn is set but never used. Initial intention was
> to use dai_posn to shorthen one code line but it looks fine
> without it too.
> 
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: SOF: compress: Remove dai_posn variable
      commit: d45f552a1e44e2885c4b7551564241959d8138be

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark