All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sameer Pujar <spujar@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: <thierry.reding@gmail.com>, <robh+dt@kernel.org>,
	<sharadg@nvidia.com>, <jonathanh@nvidia.com>,
	<kuninori.morimoto.gx@renesas.com>, <linux-tegra@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<alsa-devel@alsa-project.org>
Subject: Re: Re: Re: [PATCH v6 0/6] Tegra210 audio graph card
Date: Tue, 8 Dec 2020 20:18:21 +0530	[thread overview]
Message-ID: <a6ecb66e-db25-dcfa-4a70-d9b2fad75cd9@nvidia.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?

[Sorry I had to resend this reply. I accidentally replied from my 
personal email earlier and many people/DLs were missing on that]

WARNING: multiple messages have this Message-ID (diff)
From: Sameer Pujar <spujar@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, jonathanh@nvidia.com,
	linux-tegra@vger.kernel.org, thierry.reding@gmail.com,
	sharadg@nvidia.com
Subject: Re: Re: Re: [PATCH v6 0/6] Tegra210 audio graph card
Date: Tue, 8 Dec 2020 20:18:21 +0530	[thread overview]
Message-ID: <a6ecb66e-db25-dcfa-4a70-d9b2fad75cd9@nvidia.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?

[Sorry I had to resend this reply. I accidentally replied from my 
personal email earlier and many people/DLs were missing on that]

  parent reply	other threads:[~2020-12-08 14:49 UTC|newest]

Thread overview: 29+ 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 ` 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   ` 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   ` 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   ` Sameer Pujar
2020-11-26 18:03 ` [PATCH v6 4/6] arm64: defconfig: Enable Tegra audio graph " Sameer Pujar
2020-11-26 18:03   ` 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   ` 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-11-26 18:03   ` Sameer Pujar
2020-12-01 13:57 ` [PATCH v6 0/6] Tegra210 audio graph card Mark Brown
2020-12-01 13:57   ` Mark Brown
2020-12-07  4:52   ` Sameer Pujar
2020-12-07  4:52     ` Sameer Pujar
2020-12-07 12:31     ` Mark Brown
2020-12-07 12:31       ` Mark Brown
2020-12-08  3:54       ` Sameer Pujar
2020-12-08  3:54         ` Sameer Pujar
2020-12-08 12:13         ` Mark Brown
2020-12-08 12:13           ` Mark Brown
2020-12-08 12:46           ` Sameer Pujar
2020-12-08 14:48           ` Sameer Pujar [this message]
2020-12-08 14:48             ` Re: " Sameer Pujar
2020-12-08 15:22             ` Mark Brown
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=a6ecb66e-db25-dcfa-4a70-d9b2fad75cd9@nvidia.com \
    --to=spujar@nvidia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sharadg@nvidia.com \
    --cc=thierry.reding@gmail.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.