Message ID | 1606413823-19885-1-git-send-email-spujar@nvidia.com |
---|---|
Headers | show |
Series | Tegra210 audio graph card | expand |
On Thu, 26 Nov 2020 23:33:37 +0530, Sameer Pujar wrote: > This series adds audio graph based sound card support for Tegra210 > platforms like Jetson-TX1 an Jetson-Nano. The following preparatory > audio graph enhancement series is already merged. > * https://patchwork.kernel.org/project/alsa-devel/list/?series=375629&state=* > > Following are the summary of changes: > * Add graph/audio-graph based schemas or schema updates for Tegra210 > component and machine drivers. > * Add Tegra audio graph machine driver. > * Add required DT support for Jetson-TX1/Nano. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/3] ASoC: dt-bindings: tegra: Add graph bindings (no commit info) [2/3] ASoC: dt-bindings: tegra: Add json-schema for Tegra audio graph card (no commit info) [3/3] ASoC: tegra: Add audio graph based card driver (no commit info) All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
Hi Mark, >> This series adds audio graph based sound card support for Tegra210 >> platforms like Jetson-TX1 an Jetson-Nano. The following preparatory >> audio graph enhancement series is already merged. >> * https://patchwork.kernel.org/project/alsa-devel/list/?series=375629&state=* >> >> Following are the summary of changes: >> * Add graph/audio-graph based schemas or schema updates for Tegra210 >> component and machine drivers. >> * Add Tegra audio graph machine driver. >> * Add required DT support for Jetson-TX1/Nano. >> >> [...] > Applied to > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next > > Thanks! > > [1/3] ASoC: dt-bindings: tegra: Add graph bindings > (no commit info) > [2/3] ASoC: dt-bindings: tegra: Add json-schema for Tegra audio graph card > (no commit info) > [3/3] ASoC: tegra: Add audio graph based card driver > (no commit info) I don't see above patches in linux-next yet. Should I wait some more time for this to appear? Thanks, Sameer.
On Mon, Dec 07, 2020 at 10:22:38AM +0530, Sameer Pujar wrote: > > [1/3] ASoC: dt-bindings: tegra: Add graph bindings > > (no commit info) > > [2/3] ASoC: dt-bindings: tegra: Add json-schema for Tegra audio graph card > > (no commit info) > > [3/3] ASoC: tegra: Add audio graph based card driver > > (no commit info) > I don't see above patches in linux-next yet. Should I wait some more time > for this to appear? No, this was sent by a b4 bug - notice the "no commit info" there, they weren't applied.
>>> [1/3] ASoC: dt-bindings: tegra: Add graph bindings >>> (no commit info) >>> [2/3] ASoC: dt-bindings: tegra: Add json-schema for Tegra audio graph card >>> (no commit info) >>> [3/3] ASoC: tegra: Add audio graph based card driver >>> (no commit info) >> I don't see above patches in linux-next yet. Should I wait some more time >> for this to appear? > 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.
On Tue, Dec 08, 2020 at 09:24:47AM +0530, Sameer Pujar wrote: > > 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.
>>> 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?
>>> 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]
On Tue, Dec 08, 2020 at 08:18:21PM +0530, Sameer Pujar wrote: > > 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? Ah, yes - Rob said the dependency needed some rework.