All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: David Rhodes <drhodes@opensource.cirrus.com>
Cc: robh@kernel.org, brian.austin@cirrus.com,
	ckeepax@opensource.cirrus.com, alsa-devel@alsa-project.org,
	patches@opensource.cirrus.com,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	david.rhodes@cirrus.com
Subject: Re: [PATCH v2 1/2] ASoC: cs35l41: CS35L41 Boosted Smart Amplifier
Date: Fri, 2 Jul 2021 16:48:20 +0100	[thread overview]
Message-ID: <20210702154820.GC4416@sirena.org.uk> (raw)
In-Reply-To: <2a795a56-0b3d-069b-b31d-b8cee0b89f4f@opensource.cirrus.com>

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

On Fri, Jul 02, 2021 at 10:23:52AM -0500, David Rhodes wrote:

> So I don't think I have an actual issue, but I am just shutting up the
> static analyzers, although I do think I fixed what they were telling me.

In that case you should get the static analyzers fixed, they clearly
have a false positives problem here in what is a relatively common
pattern.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-07-02 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 22:27 [PATCH v2 0/2] Cirrus Logic CS35L41 Amplifier David Rhodes
2021-06-29 22:27 ` [PATCH v2 1/2] ASoC: cs35l41: CS35L41 Boosted Smart Amplifier David Rhodes
2021-06-29 23:51   ` Pierre-Louis Bossart
2021-06-30 21:35     ` David Rhodes
2021-07-01 11:54       ` Pierre-Louis Bossart
2021-07-01 20:22     ` David Rhodes
2021-07-02 12:08       ` Mark Brown
2021-07-02 15:23         ` David Rhodes
2021-07-02 15:48           ` Mark Brown [this message]
2021-07-02 15:52             ` David Rhodes
2021-07-12  8:32           ` Charles Keepax
2021-06-29 22:27 ` [PATCH v2 2/2] ASoC: cs35l41: Add bindings for CS35L41 David Rhodes

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=20210702154820.GC4416@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=brian.austin@cirrus.com \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=drhodes@opensource.cirrus.com \
    --cc=patches@opensource.cirrus.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=robh@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.