From: Mark Brown <broonie@kernel.org>
To: Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/14] ASoC: rt: Drop unused GPIO includes
Date: Mon, 14 Aug 2023 01:33:21 +0100 [thread overview]
Message-ID: <169197320197.2741913.755518559282925421.b4-ty@kernel.org> (raw)
In-Reply-To: <20230812-descriptors-asoc-v1-0-eb4dca1f68af@linaro.org>
On Sat, 12 Aug 2023 21:56:38 +0200, Linus Walleij wrote:
> These drivers include legacy GPIO headers for no reason
> at all, so get rid of the includes.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/14] ASoC: rt1011: Drop GPIO includes
commit: a5c8e75b34fa0d399e8e6b304de3bad4d9e41a3a
[02/14] ASoC: rt1015: Drop GPIO include
commit: c7a7f4444b1fd648edc3fb54f2d3822215b46c56
[03/14] ASoC: rt1015p: Drop legacy GPIO include
commit: 3abc7076851f63c5d193ee9d942554f182527d18
[04/14] ASoC: rt1016: Drop GPIO include
commit: 8a5a8015b1e23e41204738f2147c01bf18039965
[05/14] ASoC: rt1019: Drop GPIO include
commit: e04cbe53205ecfcb1f2a8314dfc829ebbcb542f1
[06/14] ASoC: rt1305: Drop GPIO includes
commit: ba55dde45b5a5595763af6d06066ab789792e9d3
[07/14] ASoC: rt1308: Drop GPIO includes
commit: f36c684e9941b3af6769b984239f62dc9fe99698
[08/14] ASoC: rt5514-spi: Drop GPIO include
commit: 12ffd88e398cb82f960da25ab990a6864641fee1
[09/14] ASoC: rt5514: Drop GPIO include
commit: 9fdc4feacdb0a5b3a49d611aff88371f8f8d4971
[10/14] ASoC: rt5645: Drop legacy GPIO include
commit: 92f1b48277f2fdaa9649630dc9a8ec298bfd6def
[11/14] ASoC: rt5659: Drop legacy GPIO include
commit: 0b759f3b3faa51022752bc4a99ae1af57baf344f
[12/14] ASoC: rt5660: Drop GPIO includes
commit: b72a4dc2bede787221a4b1b2e3860f6725f109b5
[13/14] ASoC: rt5682-sdw: Drop GPIO includes
commit: 1a625a7a5d74be6b367301e6eb9e38d35797313a
[14/14] ASoC: rt715: Drop GPIO includes
commit: 797df2a670c336500cdea482f404a24b45b28f45
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-08-14 0:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 19:56 Linus Walleij
2023-08-12 19:56 ` [PATCH 01/14] ASoC: rt1011: Drop " Linus Walleij
2023-08-12 19:56 ` [PATCH 02/14] ASoC: rt1015: Drop GPIO include Linus Walleij
2023-08-12 19:56 ` [PATCH 03/14] ASoC: rt1015p: Drop legacy " Linus Walleij
2023-08-12 19:56 ` [PATCH 04/14] ASoC: rt1016: Drop " Linus Walleij
2023-08-12 19:56 ` [PATCH 05/14] ASoC: rt1019: " Linus Walleij
2023-08-12 19:56 ` [PATCH 06/14] ASoC: rt1305: Drop GPIO includes Linus Walleij
2023-08-12 19:56 ` [PATCH 07/14] ASoC: rt1308: " Linus Walleij
2023-08-12 19:56 ` [PATCH 08/14] ASoC: rt5514-spi: Drop GPIO include Linus Walleij
2023-08-12 19:56 ` [PATCH 09/14] ASoC: rt5514: " Linus Walleij
2023-08-12 19:56 ` [PATCH 10/14] ASoC: rt5645: Drop legacy " Linus Walleij
2023-08-12 19:56 ` [PATCH 11/14] ASoC: rt5659: " Linus Walleij
2023-08-12 19:56 ` [PATCH 12/14] ASoC: rt5660: Drop GPIO includes Linus Walleij
2023-08-12 19:56 ` [PATCH 13/14] ASoC: rt5682-sdw: " Linus Walleij
2023-08-12 19:56 ` [PATCH 14/14] ASoC: rt715: " Linus Walleij
2023-08-14 0:33 ` 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=169197320197.2741913.755518559282925421.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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®