From: Sameer Pujar <spujar@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
thierry.reding@gmail.com, catalin.marinas@arm.com,
will@kernel.org, perex@perex.cz, tiwai@suse.com,
jonathanh@nvidia.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Mon, 6 Jun 2022 13:47:48 +0530 [thread overview]
Message-ID: <b70e024b-4f80-16b9-4bbe-ed8a24a384df@nvidia.com> (raw)
In-Reply-To: <20220603203003.GA852734-robh@kernel.org>
On 04-06-2022 02:00, Rob Herring wrote:
> Doesn't apply for me. I guess there is some undocumented dependency
> here? Resend after the merge window if that solves it.
These were getting applied fine on linux-next.
Merge window seems to have closed now and v5.19-rc1 release is out. I
can apply these cleanly on v5.19-rc1. Please let me know if re-send is
needed now or I need to wait for some more time? Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Sameer Pujar <spujar@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
catalin.marinas@arm.com, tiwai@suse.com, broonie@kernel.org,
thierry.reding@gmail.com, linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org, linux-tegra@vger.kernel.org,
jonathanh@nvidia.com, will@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Mon, 6 Jun 2022 13:47:48 +0530 [thread overview]
Message-ID: <b70e024b-4f80-16b9-4bbe-ed8a24a384df@nvidia.com> (raw)
In-Reply-To: <20220603203003.GA852734-robh@kernel.org>
On 04-06-2022 02:00, Rob Herring wrote:
> Doesn't apply for me. I guess there is some undocumented dependency
> here? Resend after the merge window if that solves it.
These were getting applied fine on linux-next.
Merge window seems to have closed now and v5.19-rc1 release is out. I
can apply these cleanly on v5.19-rc1. Please let me know if re-send is
needed now or I need to wait for some more time? Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Sameer Pujar <spujar@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
thierry.reding@gmail.com, catalin.marinas@arm.com,
will@kernel.org, perex@perex.cz, tiwai@suse.com,
jonathanh@nvidia.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Mon, 6 Jun 2022 13:47:48 +0530 [thread overview]
Message-ID: <b70e024b-4f80-16b9-4bbe-ed8a24a384df@nvidia.com> (raw)
In-Reply-To: <20220603203003.GA852734-robh@kernel.org>
On 04-06-2022 02:00, Rob Herring wrote:
> Doesn't apply for me. I guess there is some undocumented dependency
> here? Resend after the merge window if that solves it.
These were getting applied fine on linux-next.
Merge window seems to have closed now and v5.19-rc1 release is out. I
can apply these cleanly on v5.19-rc1. Please let me know if re-send is
needed now or I need to wait for some more time? Thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-06 8:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 6:36 [PATCH v3 0/6] OPE support on Tegra210 and later Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` [PATCH v3 1/6] ASoC: tegra: Add binding doc for OPE module Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 20:30 ` Rob Herring
2022-06-03 20:30 ` Rob Herring
2022-06-03 20:30 ` Rob Herring
2022-06-06 8:17 ` Sameer Pujar [this message]
2022-06-06 8:17 ` Sameer Pujar
2022-06-06 8:17 ` Sameer Pujar
2022-06-06 13:48 ` Rob Herring
2022-06-06 13:48 ` Rob Herring
2022-06-06 13:48 ` Rob Herring
2022-06-03 6:36 ` [PATCH v3 2/6] ASoC: tegra: Add Tegra210 based OPE driver Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` [PATCH v3 3/6] ASoC: tegra: AHUB routes for OPE module Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` [PATCH v3 4/6] arm64: defconfig: Build Tegra " Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` [PATCH v3 5/6] arm64: tegra: Add OPE device on Tegra210 and later Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` [PATCH v3 6/6] arm64: tegra: Enable OPE on various platforms Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-03 6:36 ` Sameer Pujar
2022-06-07 10:55 ` (subset) [PATCH v3 0/6] OPE support on Tegra210 and later Mark Brown
2022-06-07 10:55 ` Mark Brown
2022-06-07 10:55 ` 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=b70e024b-4f80-16b9-4bbe-ed8a24a384df@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=will@kernel.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 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.