From: Dan Murphy <dmurphy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <perex@perex.cz>, <tiwai@suse.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<robh@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 3/7] ASoC: tas2562: Fix format issue for extra space before a comma
Date: Wed, 24 Jun 2020 12:51:57 -0500 [thread overview]
Message-ID: <d2227f18-7585-d5a2-8438-57ee8717318a@ti.com> (raw)
In-Reply-To: <20200624174813.GN5472@sirena.org.uk>
Mark
On 6/24/20 12:48 PM, Mark Brown wrote:
> On Wed, Jun 24, 2020 at 12:36:02PM -0500, Dan Murphy wrote:
>
>> Can this patchset get a review as well so I can fix before I post v6?
>> Not sure what the current work load is for review or merge.
> Well, it's less work to review if it's been fixed...
Ok fixed and sent v6
next prev parent reply other threads:[~2020-06-24 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 16:14 [PATCH v5 0/7] TAS2562 issue fixes and slot programming Dan Murphy
2020-06-24 16:14 ` [PATCH v5 1/7] dt-bindings: tas2562: Fix shut-down gpio property Dan Murphy
2020-06-24 16:14 ` [PATCH v5 2/7] ASoC: tas2562: Update shutdown GPIO property Dan Murphy
2020-06-24 16:14 ` [PATCH v5 3/7] ASoC: tas2562: Fix format issue for extra space before a comma Dan Murphy
2020-06-24 16:29 ` Mark Brown
2020-06-24 16:58 ` Dan Murphy
2020-06-24 17:36 ` Dan Murphy
2020-06-24 17:48 ` Mark Brown
2020-06-24 17:51 ` Dan Murphy [this message]
2020-06-24 16:14 ` [PATCH v5 4/7] ASoC: tas2562: Add rx and tx slot programming Dan Murphy
2020-06-24 16:14 ` [PATCH v5 5/7] dt-bindings: tas2562: Add voltage sense slot property Dan Murphy
2020-06-24 16:14 ` [PATCH v5 6/7] ASoC: tas2562: Add voltage sense slot configuration Dan Murphy
2020-06-24 16:14 ` [PATCH v5 7/7] dt-bindings: tas2562: Convert the tas2562 binding to yaml Dan Murphy
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=d2227f18-7585-d5a2-8438-57ee8717318a@ti.com \
--to=dmurphy@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®