From: "Rojewski, Cezary" <cezary.rojewski@intel.com>
To: "Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Łukasz Majczak" <lma@semihalf.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Guenter Roeck" <groeck@google.com>,
"Radoslaw Biernacki" <rad@semihalf.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Liam Girdwood" <liam.r.girdwood@linux.intel.com>,
"Mateusz Gorski" <mateusz.gorski@linux.intel.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Alex Levin" <levinale@google.com>
Subject: RE: [PATCH v2] ASoC: Intel: Skylake: Check the kcontrol against NULL
Date: Wed, 20 Jan 2021 16:45:38 +0000 [thread overview]
Message-ID: <4774f65a7f2f464781a45790c8934a62@intel.com> (raw)
In-Reply-To: <371e612ac59c458cad1bafb82ca09c9f@intel.com>
On 2021-01-20 5:41 PM, Rojewski, Cezary wrote:
>
> Just checked the history behind this. And must say, I liked Ricardo's
> version better. Except for the "= {};" bit which Mark already pointed
> out - it should be a separate fix - it's simply more optional
Meant to say: optimal.
WARNING: multiple messages have this Message-ID (diff)
From: "Rojewski, Cezary" <cezary.rojewski@intel.com>
To: "Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Łukasz Majczak" <lma@semihalf.com>
Cc: "Marcin Wojtas" <mw@semihalf.com>,
"Liam Girdwood" <liam.r.girdwood@linux.intel.com>,
"Mateusz Gorski" <mateusz.gorski@linux.intel.com>,
"Radoslaw Biernacki" <rad@semihalf.com>,
"Alex Levin" <levinale@google.com>,
"Guenter Roeck" <groeck@google.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: RE: [PATCH v2] ASoC: Intel: Skylake: Check the kcontrol against NULL
Date: Wed, 20 Jan 2021 16:45:38 +0000 [thread overview]
Message-ID: <4774f65a7f2f464781a45790c8934a62@intel.com> (raw)
In-Reply-To: <371e612ac59c458cad1bafb82ca09c9f@intel.com>
On 2021-01-20 5:41 PM, Rojewski, Cezary wrote:
>
> Just checked the history behind this. And must say, I liked Ricardo's
> version better. Except for the "= {};" bit which Mark already pointed
> out - it should be a separate fix - it's simply more optional
Meant to say: optimal.
next prev parent reply other threads:[~2021-01-20 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 12:14 [PATCH] ASoC: Intel: Skylake: Check the kcontrol against NULL Lukasz Majczak
2020-12-10 12:14 ` Lukasz Majczak
2020-12-10 15:55 ` Gorski, Mateusz
2020-12-10 15:55 ` Gorski, Mateusz
2020-12-10 16:01 ` Guenter Roeck
2020-12-11 15:42 ` Amadeusz Sławiński
2020-12-17 13:04 ` [PATCH v2] " Lukasz Majczak
2020-12-17 13:04 ` Lukasz Majczak
2021-01-12 11:34 ` Łukasz Majczak
2021-01-12 11:34 ` Łukasz Majczak
2021-01-20 15:49 ` Łukasz Majczak
2021-01-20 15:49 ` Łukasz Majczak
2021-01-20 16:33 ` Pierre-Louis Bossart
2021-01-20 16:33 ` Pierre-Louis Bossart
2021-01-20 16:41 ` Rojewski, Cezary
2021-01-20 16:41 ` Rojewski, Cezary
2021-01-20 16:45 ` Rojewski, Cezary [this message]
2021-01-20 16:45 ` Rojewski, Cezary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4774f65a7f2f464781a45790c8934a62@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=groeck@google.com \
--cc=levinale@google.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lma@semihalf.com \
--cc=mateusz.gorski@linux.intel.com \
--cc=mw@semihalf.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rad@semihalf.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.