mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	liweilei@awinic.com, u.kleine-koenig@pengutronix.de,
	yang.lee@linux.alibaba.com, nathan@kernel.org,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	wangweidong.a@awinic.com
Subject: Re: [PATCH V2 0/3] ASoC: codecs: Modify some error codes
Date: Thu, 02 Nov 2023 14:26:25 +0000	[thread overview]
Message-ID: <169893518558.36738.243491245634528224.b4-ty@kernel.org> (raw)
In-Reply-To: <20231101090211.177125-1-wangweidong.a@awinic.com>

On Wed, 01 Nov 2023 17:02:07 +0800, wangweidong.a@awinic.com wrote:
> The maximum value that calib can set should be
> consistent with the maximum value of re.
> 
> An error code should be return when the re is greater
> than the maximum value or less than the minimum value
> 
> The value of vsense_select should be either 32
> or 0 in both cases, so modify the
> AW88399_DEV_VDSEL_VSENSE macro to 32.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: codecs: Modify the maximum value of calib
      commit: c9e920ffa752b9047d65041cd70495409c768dd7
[2/3] ASoC: codecs: Modify the wrong judgment of re value
      commit: baf46c3c763809fbeabcff5ec6e2ff3081f755f2
[3/3] ASoC: codecs: Modify macro value error
      commit: b729598c1747576bb9a4c997190be3f7c2915726

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


      parent reply	other threads:[~2023-11-02 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  9:02 wangweidong.a
2023-11-01  9:02 ` [PATCH V2 1/3] ASoC: codecs: Modify the maximum value of calib wangweidong.a
2023-11-01  9:02 ` [PATCH V2 2/3] ASoC: codecs: Modify the wrong judgment of re value wangweidong.a
2023-11-01  9:02 ` [PATCH V2 3/3] ASoC: codecs: Modify macro value error wangweidong.a
2023-11-02 14:26 ` 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=169893518558.36738.243491245634528224.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --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=u.kleine-koenig@pengutronix.de \
    --cc=wangweidong.a@awinic.com \
    --cc=yang.lee@linux.alibaba.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®