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:     derek.fang@realtek.com, lgirdwood@gmail.com
Cc:     Mark Brown <broonie@kernel.org>, robh+dt@kernel.org,
        flove@realtek.com, alsa-devel@alsa-project.org,
        devicetree@vger.kernel.org, jack.yu@realtek.com,
        linux-kernel@vger.kernel.org, lars@metafoo.de,
        shumingf@realtek.com, oder_chiou@realtek.com
Subject: Re: [PATCH] ASoC: dt-bindings: rt5682s: fix the device-tree schema errors
Date:   Thu, 30 Sep 2021 15:58:54 +0100
Message-Id: <163301248178.43045.15903836903409128227.b4-ty@kernel.org>
In-Reply-To: <20210929130406.24325-1-derek.fang@realtek.com>
References: <20210929130406.24325-1-derek.fang@realtek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 29 Sep 2021 21:04:06 +0800, derek.fang@realtek.com wrote:
> From: Derek Fang <derek.fang@realtek.com>
> 
> Fix the device-tree schema errors that be reported by using 'make
> dt_binding_check'.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: rt5682s: fix the device-tree schema errors
      commit: 91cf45595021bd6f6279748aa472de7fc7864084

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