All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	Sameer Pujar <spujar@nvidia.com>,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	alsa-devel@alsa-project.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: (subset) [PATCH 0/2] arm64: tegra: Enable audio IOMMU support on Tegra194
Date: Thu, 1 Jul 2021 13:51:34 +0100	[thread overview]
Message-ID: <20210701125134.GB4641@sirena.org.uk> (raw)
In-Reply-To: <YNylGG9RaM72CY2i@orome.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 389 bytes --]

On Wed, Jun 30, 2021 at 07:08:40PM +0200, Thierry Reding wrote:

> Could you drop this patch from your queue at this time? I can send out
> the updated patch once I'm convinced it isn't going to regress further.

OK since it's the top commit, in general it's better to send reverts for
things like this though - like some other people I rarely rebase or
otherwise modify existing commits.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	Sameer Pujar <spujar@nvidia.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-tegra@vger.kernel.org
Subject: Re: (subset) [PATCH 0/2] arm64: tegra: Enable audio IOMMU support on Tegra194
Date: Thu, 1 Jul 2021 13:51:34 +0100	[thread overview]
Message-ID: <20210701125134.GB4641@sirena.org.uk> (raw)
In-Reply-To: <YNylGG9RaM72CY2i@orome.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 389 bytes --]

On Wed, Jun 30, 2021 at 07:08:40PM +0200, Thierry Reding wrote:

> Could you drop this patch from your queue at this time? I can send out
> the updated patch once I'm convinced it isn't going to regress further.

OK since it's the top commit, in general it's better to send reverts for
things like this though - like some other people I rarely rebase or
otherwise modify existing commits.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-07-01 12:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 18:11 [PATCH 0/2] arm64: tegra: Enable audio IOMMU support on Tegra194 Thierry Reding
2021-06-28 18:11 ` Thierry Reding
2021-06-28 18:11 ` [PATCH 1/2] ASoC: tegra: Use ADMAIF component for DMA allocations Thierry Reding
2021-06-28 18:11   ` Thierry Reding
2021-06-28 18:11 ` [PATCH 2/2] arm64: tegra: Enable audio IOMMU support on Tegra194 Thierry Reding
2021-06-28 18:11   ` Thierry Reding
2021-06-30 16:10 ` (subset) [PATCH 0/2] " Mark Brown
2021-06-30 16:10   ` Mark Brown
2021-06-30 17:08   ` Thierry Reding
2021-06-30 17:08     ` Thierry Reding
2021-07-01 12:51     ` Mark Brown [this message]
2021-07-01 12:51       ` 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=20210701125134.GB4641@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=spujar@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.