From: Dan Murphy <dmurphy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <perex@perex.cz>, <tiwai@suse.com>,
<robh@kernel.org>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] ASoC: tas2562: Update shutdown GPIO property
Date: Tue, 23 Jun 2020 12:20:32 -0500 [thread overview]
Message-ID: <63eb06e7-451d-0e8f-36fb-5b5d93ccf803@ti.com> (raw)
In-Reply-To: <20200623171842.GH5582@sirena.org.uk>
Mark
On 6/23/20 12:18 PM, Mark Brown wrote:
> On Tue, Jun 23, 2020 at 10:59:49AM -0500, Dan Murphy wrote:
>> On 6/12/20 12:14 PM, Dan Murphy wrote:
>>> Update the shutdown GPIO property to be shutdown from shut-down.
>> I have some other patches that go on top of this patchset I am wondering if
>> I should re-submit with those patches on top or indicate in a cover letter
>> the dependency
> If you decide to resubmit please make the YAML conversion the very last
> thing you do in your series, there is a considerable backlog on YAML
> conversion reviews which slows down any changes that depend on them.
Thanks for the advice. I know the DT folks have a lot to review and the
merge window did not help them.
I will re-factor these and re-submit as well as the TAS2770 patchset.
Dan
next prev parent reply other threads:[~2020-06-23 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 17:14 [PATCH v4 1/2] dt-bindings: tas2562: Convert the tas2562 binding to yaml Dan Murphy
2020-06-12 17:14 ` [PATCH v4 2/2] ASoC: tas2562: Update shutdown GPIO property Dan Murphy
2020-06-23 15:59 ` Dan Murphy
2020-06-23 17:18 ` Mark Brown
2020-06-23 17:20 ` Dan Murphy [this message]
2020-07-28 16:30 ` [PATCH v4 1/2] dt-bindings: tas2562: Convert the tas2562 binding to yaml Mark Brown
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=63eb06e7-451d-0e8f-36fb-5b5d93ccf803@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;
as well as URLs for NNTP newsgroup(s).