From: Sameer Pujar <dev.spujar@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH v6 0/6] Tegra210 audio graph card
Date: Tue, 8 Dec 2020 18:16:06 +0530 [thread overview]
Message-ID: <55d1934e-d3f0-8765-341b-a853662b3f70@gmail.com> (raw)
In-Reply-To: <20201208121312.GB6686@sirena.org.uk>
>>> No, this was sent by a b4 bug - notice the "no commit info" there, they
>>> weren't applied.
>> Oh I see! I guess review would be still pending then.
> I don't seem to have them in my backlog so either there was feedback
> from someone else I was expecting to see addressed or some other issue.
I am pretty sure that it is not because of any outstanding comments,
because I got none on v6 and previous v5 feedback was taken care. May be
this is because of the doc dependency I listed in the cover letter?
next prev parent reply other threads:[~2020-12-08 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 18:03 [PATCH v6 0/6] Tegra210 audio graph card Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 1/6] ASoC: dt-bindings: tegra: Add graph bindings Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 2/6] ASoC: dt-bindings: tegra: Add json-schema for Tegra audio graph card Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 3/6] ASoC: tegra: Add audio graph based card driver Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 4/6] arm64: defconfig: Enable Tegra audio graph " Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 5/6] arm64: tegra: Audio graph header for Tegra210 Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 6/6] arm64: tegra: Audio graph sound card for Jetson Nano and TX1 Sameer Pujar
2020-12-01 13:57 ` [PATCH v6 0/6] Tegra210 audio graph card Mark Brown
2020-12-07 4:52 ` Sameer Pujar
2020-12-07 12:31 ` Mark Brown
2020-12-08 3:54 ` Sameer Pujar
2020-12-08 12:13 ` Mark Brown
2020-12-08 12:46 ` Sameer Pujar [this message]
2020-12-08 14:48 ` Sameer Pujar
2020-12-08 15:22 ` 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=55d1934e-d3f0-8765-341b-a853662b3f70@gmail.com \
--to=dev.spujar@gmail.com \
--cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox