From: Colin Ian King <colin.king@canonical.com>
To: Mark Brown <broonie@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Sangbeom Kim <sbkim73@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] ASoC: samsung: remove redundant pointer cpu_dai
Date: Tue, 13 Mar 2018 16:22:41 +0000 [thread overview]
Message-ID: <1db711ff-63ba-7a0e-dc9d-33638bd4a0d9@canonical.com> (raw)
In-Reply-To: <20180313162138.GQ2186@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 422 bytes --]
On 13/03/18 16:21, Mark Brown wrote:
> On Tue, Mar 13, 2018 at 01:36:26PM +0000, Colin King wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> The pointer cpu_dai is assigned a value but the pointer is never
>> read, hence it is redundant and can be removed.
>
> There's some subsequent patches to that driver which I think provide an
> alternative fix for this.
>
OK, glad it's been resolved.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next prev parent reply other threads:[~2018-03-13 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 13:36 [PATCH][next] ASoC: samsung: remove redundant pointer cpu_dai Colin King
2018-03-13 16:21 ` Mark Brown
2018-03-13 16:21 ` Mark Brown
2018-03-13 16:21 ` Mark Brown
2018-03-13 16:22 ` Colin Ian King [this message]
2018-03-14 17:45 ` [alsa-devel] " kbuild test robot
2018-03-14 17:45 ` kbuild test robot
2018-03-14 17:45 ` [alsa-devel] " kbuild test robot
2018-03-14 18:08 ` kbuild test robot
2018-03-14 18:08 ` kbuild test robot
2018-03-14 18:08 ` [alsa-devel] " kbuild test robot
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=1db711ff-63ba-7a0e-dc9d-33638bd4a0d9@canonical.com \
--to=colin.king@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=s.nawrocki@samsung.com \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.com \
/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.