lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1317127128.7207.1.camel@phoenix>
Date:	Tue, 27 Sep 2011 20:38:48 +0800
From:	Axel Lin <axel.lin@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Jonathan Cameron <jic23@....ac.uk>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...com>, alsa-devel@...a-project.org
Subject: [PATCH 0/6] ASoC: Remove unused control_data field from private
 struct

This serial removes unused control_data field from private struct.
The control_data field is used to initialize the codec's control_data field,
but since this is also done by the snd-soc-cache core, the redundant
assignment can be removed and the field can be dropped.

Note: I don't have these hardware, only compile test on these patches.

Axel Lin (6):
  ASoC: Remove unused "control_data" field of struct wm8904_priv
  ASoC: Remove unused "control_data" field of struct wm8940_priv
  ASoC: Remove unused "control_data" field of struct wm8960_priv
  ASoC: Remove unused "control_data" field of struct wm8978_priv
  ASoC: Remove unused "control_data" field of struct wm9081_priv
  ASoC: Remove unused "control_data" field of struct wm9090_priv

 sound/soc/codecs/wm8904.c |    2 --
 sound/soc/codecs/wm8940.c |    3 ---
 sound/soc/codecs/wm8960.c |    3 ---
 sound/soc/codecs/wm8978.c |    3 ---
 sound/soc/codecs/wm9081.c |    3 ---
 sound/soc/codecs/wm9090.c |    3 ---
 6 files changed, 0 insertions(+), 17 deletions(-)

-- 
1.7.4.1



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ