From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
liweilei@awinic.com, yijiangtao@awinic.com, trix@redhat.com,
dan.carpenter@linaro.org, colin.i.king@gmail.com,
herve.codina@bootlin.com, nathan@kernel.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
wangweidong.a@awinic.com
Subject: Re: [PATCH] ASoC: codecs: Modify the bin file parsing method
Date: Mon, 13 Nov 2023 14:05:34 +0000 [thread overview]
Message-ID: <169988433475.3280890.6431768329803223556.b4-ty@kernel.org> (raw)
In-Reply-To: <20231109093708.13155-1-wangweidong.a@awinic.com>
On Thu, 09 Nov 2023 17:37:07 +0800, wangweidong.a@awinic.com wrote:
> Modify the aw88395_lib file so that the bin file
> parsing is no longer related to the chip id of the chip.
> Adopt the bin file data type "prof_data_type" as the
> differentiation between different chip bin file
> parsing methods.
>
> Since the chip id macro for the aw88399 is no longer
> defined in aw88395_reg.h, define the chip id
> for the aw88399 in aw88399.h
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: codecs: Modify the bin file parsing method
commit: fc213b8d4466d1fcf39ab760979be4eac2a67635
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
prev parent reply other threads:[~2023-11-13 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 9:37 wangweidong.a
2023-11-13 14:05 ` Mark Brown [this message]
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=169988433475.3280890.6431768329803223556.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=herve.codina@bootlin.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=liweilei@awinic.com \
--cc=nathan@kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=trix@redhat.com \
--cc=wangweidong.a@awinic.com \
--cc=yijiangtao@awinic.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
all inboxes | Powered by JetHome®