ASoC: codecs: aw88261: pass pointer directly instead of passing the address
Subsystems (3)
PATCH 1/1 ASoC: codecs: aw88261: pass pointer directly instead of passing the address
It's a little bit cleaner to just pass "aw88261" instead of the address of it "&aw88261".
--- sound/soc/codecs/aw88261.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
sound/soc/codecs/aw88261.c +4 -4
@@ -1184,7 +1184,7 @@ static void aw88261_parse_channel_dt(struct aw88261 *aw88261) aw_dev->channel = channel_value; } -static int aw88261_init (struct aw88261 **aw88261,struct i2c_client *i2c,struct regmap *regmap) +static int aw88261_init (struct aw88261 *aw88261,struct i2c_client *i2c,struct regmap *regmap) {struct aw_device *aw_dev;unsigned int chip_id;
@@ -1207,7 +1207,7 @@ static int aw88261_init(struct aw88261 **aw88261, struct i2c_client *i2c, structif (!aw_dev)return -ENOMEM ; - (*aw88261)->aw_pa = aw_dev; + aw88261->aw_pa = aw_dev; aw_dev->i2c = i2c; aw_dev->regmap = regmap; aw_dev->dev = &i2c->dev;
@@ -1221,7 +1221,7 @@ static int aw88261_init(struct aw88261 **aw88261, struct i2c_client *i2c, struct aw_dev->fade_step =AW88261_VOLUME_STEP_DB ; aw_dev->volume_desc.ctl_volume =AW88261_VOL_DEFAULT_VALUE ; aw_dev->volume_desc.mute_volume =AW88261_MUTE_VOL ; -aw88261_parse_channel_dt (*aw88261); +aw88261_parse_channel_dt (aw88261);return ret; }
@@ -1250,7 +1250,7 @@ static int aw88261_i2c_probe(struct i2c_client *i2c) }/* aw pa init */ - ret =aw88261_init (&aw88261, i2c, aw88261->regmap); + ret =aw88261_init (aw88261, i2c, aw88261->regmap);if (ret)return ret;
Signature · 1 line
2.51.0
Mark Brown
maintainerQuoted 4 lines · Dan Carpenter
It's a little bit cleaner to just pass "aw88261" instead of the address of it "&aw88261".
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: codecs: aw88261: pass pointer directly instead of passing the address
commit: 84194c66aaf78fed150edb217b9f341518b1cba2
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