[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167328296387.323147.13503501873673996744.b4-ty@kernel.org>
Date: Mon, 09 Jan 2023 16:49:23 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org,
Ajye Huang <ajye_huang@...pal.corp-partner.google.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Sean Paul <sean@...rly.run>,
Terry Cheong <htcheong@...omium.org>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Sasha Levin <sashal@...nel.org>,
Lucas Tanure <tanureal@...nsource.cirrus.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Ryan Lee <ryan.lee.analog@...il.com>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Jaroslav Kysela <perex@...ex.cz>,
David Lin <CTLIN0@...oton.com>, Brent Lu <brent.lu@...el.com>,
Takashi Iwai <tiwai@...e.com>,
Linux Patches Robot
<linux-patches-robot@...omeos-missing-patches.google.com.iam.gserviceaccount.com>,
amadeuszx.slawinski@...ux.intel.com, alsa-devel@...a-project.org,
kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v1] ASoC: nau8315: remove dependency on GPIOLIB
On Sun, 08 Jan 2023 19:43:51 +0800, Ajye Huang wrote:
> commit dcc2c012c7691 ("ASoC: Fix gpiolib dependencies") removed a
> series of unnecessary dependencies on GPIOLIB when the gpio was
> optional.
>
> A similar simplification seems valid for nau8315, so remove the
> dependency as well. This will avoid the following warning
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: nau8315: remove dependency on GPIOLIB
commit: 523ba3b70fc572f69673d8bd88af00df0e716529
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
Powered by blists - more mailing lists