[PATCH v2] ASoC: fsl_esai: Remove unused 'imx' field

[PATCH v2] ASoC: fsl_esai: Remove unused 'imx' field

[Fabio Estevam]

The 'imx' field is not used anywhere, so get rid of it.

Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
Changes since v1:
- Also remove the comment about the imx member.

 sound/soc/fsl/fsl_esai.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c
index bac9f059c9fc..08056fa0a0fa 100644
--- a/sound/soc/fsl/fsl_esai.c
+++ b/sound/soc/fsl/fsl_esai.c
@@ -23,11 +23,9 @@
 
 /**
  * struct fsl_esai_soc_data - soc specific data
- * @imx: for imx platform
  * @reset_at_xrun: flags for enable reset operaton
  */
 struct fsl_esai_soc_data {
-	bool imx;
 	bool reset_at_xrun;
 };
 
@@ -86,17 +84,14 @@ struct fsl_esai {
 };
 
 static struct fsl_esai_soc_data fsl_esai_vf610 = {
-	.imx = false,
 	.reset_at_xrun = true,
 };
 
 static struct fsl_esai_soc_data fsl_esai_imx35 = {
-	.imx = true,
 	.reset_at_xrun = true,
 };
 
 static struct fsl_esai_soc_data fsl_esai_imx6ull = {
-	.imx = true,
 	.reset_at_xrun = false,
 };
 
-- 
2.25.1

Re: [PATCH v2] ASoC: fsl_esai: Remove unused 'imx' field

[Shengjiu Wang]

On Sat, Feb 6, 2021 at 10:28 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> The 'imx' field is not used anywhere, so get rid of it.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>

Acked-by: Shengjiu Wang <shengjiu.wang@gmail.com>

Re: [PATCH v2] ASoC: fsl_esai: Remove unused 'imx' field

[Mark Brown]

On Sat, 6 Feb 2021 11:27:53 -0300, Fabio Estevam wrote:
> The 'imx' field is not used anywhere, so get rid of it.

Applied to

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

Thanks!

[1/1] ASoC: fsl_esai: Remove unused 'imx' field
      commit: 40bd053bc8e18b68e877bd4cdea1b6938ddf5fdd

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