[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37669247-daaf-c6cb-0ef2-464e61db9838@gmail.com>
Date: Fri, 24 Jan 2020 07:28:52 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Sameer Pujar <spujar@...dia.com>, perex@...ex.cz, tiwai@...e.com,
robh+dt@...nel.org
Cc: devicetree@...r.kernel.org, alsa-devel@...a-project.org,
atalambedu@...dia.com, linux-kernel@...r.kernel.org,
lgirdwood@...il.com, jonathanh@...dia.com, viswanathl@...dia.com,
sharadg@...dia.com, broonie@...nel.org, thierry.reding@...il.com,
linux-tegra@...r.kernel.org, rlokhande@...dia.com,
mkumard@...dia.com, dramesh@...dia.com
Subject: Re: [alsa-devel] [PATCH 5/9] ASoC: tegra: add Tegra210 based AHUB
driver
24.01.2020 06:39, Sameer Pujar пишет:
>>> +static int tegra_ahub_put_value_enum(struct snd_kcontrol *kctl,
>>> + struct snd_ctl_elem_value *uctl)
>>> +{
>>> + struct snd_soc_component *cmpnt =
>>> snd_soc_dapm_kcontrol_component(kctl);
>>> + struct tegra_ahub *ahub = snd_soc_component_get_drvdata(cmpnt);
>>> + struct snd_soc_dapm_context *dapm =
>>> snd_soc_dapm_kcontrol_dapm(kctl);
>>> + struct soc_enum *e = (struct soc_enum *)kctl->private_value;
>>> + struct snd_soc_dapm_update update[TEGRA_XBAR_UPDATE_MAX_REG] =
>>> { };
>> Shouldn't this be {0} to make array zero'ed?
>
> Isn't it the same with empty braces?
Looks like is should be the same because turns out GCC has an extension
for that.
Powered by blists - more mailing lists