Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     krzysztof.kozlowski@canonical.com, cgel.zte@gmail.com
Cc:     Minghao Chi <chi.minghao@zte.com.cn>, s.nawrocki@samsung.com,
        tiwai@suse.com, lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
        perex@perex.cz, alsa-devel@alsa-project.org,
        Zeal Robot <zealci@zte.com.cn>
In-Reply-To: <20220117110357.863990-1-chi.minghao@zte.com.cn>
References: <20220117110357.863990-1-chi.minghao@zte.com.cn>
Subject: Re: [PATCH] sound/soc/samsung: remove unneeded ret variable
Message-Id: <164310602383.74844.16089601402972484181.b4-ty@kernel.org>
Date:   Tue, 25 Jan 2022 10:20:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 17 Jan 2022 11:03:57 +0000, cgel.zte@gmail.com wrote:
> From: Minghao Chi <chi.minghao@zte.com.cn>
> 
> Return value from io_remap_pfn_range() directly instead
> of taking this in another redundant variable.
> 
> 

Applied to

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

Thanks!

[1/1] sound/soc/samsung: remove unneeded ret variable
      commit: de531908ca4251918f3aff4b21440a8f7b96b0b7

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