From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/6] ASoC: rt5682: apply some refactors
Date: Thu, 30 Apr 2020 14:40:06 +0100 [thread overview]
Message-ID: <158825399443.18388.8084026122456851168.b4-ty@kernel.org> (raw)
In-Reply-To: <20200430082231.151127-1-tzungbi@google.com>
On Thu, 30 Apr 2020 16:22:25 +0800, Tzung-Bi Shih wrote:
> The series tries to refactor the coding style to follow most conventions.
>
> The 4th patch converts pr_() to dev_().
> (https://mailman.alsa-project.org/pipermail/alsa-devel/2020-March/164849.html)
>
> The 6th patch changes the behavior a bit to restore its original intent.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.8
Thanks!
[1/6] ASoC: rt5682: simplify assertions
commit: 38c2e325a66b1c4d694d2a15b5efa81e5ae38872
[2/6] ASoC: rt5682: fix space issues
commit: 5b8e09091b6092296a209a940e192ed2cc891efe
[3/6] ASoC: rt5682: remove empty default case
commit: 70255cf6917828a2caf93f79f15a09bd71803e61
[4/6] ASoC: rt5682: replace message printing from pr_() to dev_()
commit: 9c1cb755b5b325c18551f7d08438ea6896130acd
[5/6] ASoC: rt5682: remove duplicate rt5682_reset() calls
commit: 2317e84979fb80821c0d3ef909f1a2b68ace37f9
[6/6] ASoC: rt5682: remove unwanted btn_type assignment
commit: 4642126b852f46d5d6a16bc60d50fbe4920c2710
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:[~2020-04-30 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 8:22 [PATCH 0/6] ASoC: rt5682: apply some refactors Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 1/6] ASoC: rt5682: simplify assertions Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 2/6] ASoC: rt5682: fix space issues Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 3/6] ASoC: rt5682: remove empty default case Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 4/6] ASoC: rt5682: replace message printing from pr_() to dev_() Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 5/6] ASoC: rt5682: remove duplicate rt5682_reset() calls Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 6/6] ASoC: rt5682: remove unwanted btn_type assignment Tzung-Bi Shih
2020-04-30 13:40 ` 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=158825399443.18388.8084026122456851168.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=tzungbi@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.