Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 16 Feb 2022 15:23:27 +0100
From:   Thierry Reding <thierry.reding@gmail.com>
To:     Takashi Iwai <tiwai@suse.de>
Cc:     Mohan Kumar <mkumard@nvidia.com>, broonie@kernel.org,
        lgirdwood@gmail.com, robh+dt@kernel.org, tiwai@suse.com,
        jonathanh@nvidia.com, spujar@nvidia.com,
        alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
        linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Add Tegra234 HDA support
Message-ID: <Yg0I312RA5gh1Rra@orome>
References: <20220210065057.13555-1-mkumard@nvidia.com>
 <s5hmtiscl65.wl-tiwai@suse.de>
 <s5hk0dwckza.wl-tiwai@suse.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="WpdOLmAFG2mpJZKT"
Content-Disposition: inline
In-Reply-To: <s5hk0dwckza.wl-tiwai@suse.de>
User-Agent: Mutt/2.2 (7160e05a) (2022-02-12)
Precedence: bulk


--WpdOLmAFG2mpJZKT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 15, 2022 at 02:34:01PM +0100, Takashi Iwai wrote:
> On Tue, 15 Feb 2022 14:29:54 +0100,
> Takashi Iwai wrote:
> >=20
> > On Thu, 10 Feb 2022 07:50:51 +0100,
> > Mohan Kumar wrote:
> > >=20
> > > This series add the support for TEGRA234 HDA driver support
> > >=20
> > > Mohan Kumar (6):
> > >   ALSA: hda/tegra: Add Tegra234 hda driver support
> > >   ALSA: hda/tegra: Hardcode GCAP ISS value on T234
> > >   ALSA: hda/tegra: Update scratch reg. communication
> > >   dt-bindings: Add HDA support for Tegra234
> > >   dt-bindings: Document Tegra234 HDA support
> > >   arm64: tegra: Add hda dts node for Tegra234
> >=20
> > Applied all six patches to for-next branch now.
>=20
> ... and now I realized that it's conflicting with the latest Tegra234
> reset stuff on linux-next.
>=20
> Maybe better to split the patches to be merged through several trees?

It's usually best for me to pick up at least the DT changes (patch 6)
into the Tegra tree, that way I can easily resolve conflicts there when
they arise.

The device tree bindings (patches 3 & 4) traditionally go along with
the driver changes, though.

If you prefer the patch series to be split, that's fine. For other
subsystems we usually deal with this by having one series and then the
subsystem maintainer picking up all the non-DT changes and I take the
rest.

Thierry

--WpdOLmAFG2mpJZKT
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAmINCNwACgkQ3SOs138+
s6EXuw/9F6JKANiIO2CI2JqhaJ2UxIofJCAM5RgH9vFvU5emWUcF9WDUvAx6C967
rd5ThJkit9WTy+Am+40xvky1siWsoQ3K3VfNI2oH6ZqTmM7aE62DF7eqUcz7Cwp/
k+09/jx+ESF9Pvrirk06EtPsKpz2nJmvqNEoZ4/81mAkyZBYK9lHp7GPUpYusxfq
t7bq9ru4sOyV/PA6sPeellMCmr5OBhoIs/GH4R0P0WimCG5+KP9rPQSGHX6ec3XL
WB4vQLAyHU+2kyuCq+Y4JQeprlkrIS1oeke8En7uRsH7gTOvdjonwZ5M2ttvOC6r
Vj3Sky6S+IirTA42LAVoPweJy4ZtygB7yeTc1xwO0vGBD0SlLocCmNmlvagbF/eK
ERlMgwT2XinPvtsJav0hrxB3yDN4qnkbUaK7GB+ixoiZ97HKhEqknAI9nA3QLjV0
Klgqr+HRURMYdOhUgQ+fUbV8yqcTidI+tjz1N9XTvhudlM9/jYTx1Y81WhPejqt+
NAV4PFWmn1iFaKDtlxl9owqkOmaaiwNiy/e6CCUIb7uF3t/ro0gayrW55gutW704
BT59C8XFocHSE8WO+6Ak7tADGUxgWZDw+evIXpkEPODEmI+AlSRMQrw//L0c7Xqe
bYqQyKtukPxQ6glL9fueg6OIFy/xQYxysXxMmk+1e0nRFHmyx48=
=tDWF
-----END PGP SIGNATURE-----

--WpdOLmAFG2mpJZKT--