linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Wed, 16 Feb 2022 15:23:27 +0100	[thread overview]
Message-ID: <Yg0I312RA5gh1Rra@orome> (raw)
In-Reply-To: <s5hk0dwckza.wl-tiwai@suse.de>

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

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:
> > 
> > On Thu, 10 Feb 2022 07:50:51 +0100,
> > Mohan Kumar wrote:
> > > 
> > > This series add the support for TEGRA234 HDA driver support
> > > 
> > > 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
> > 
> > Applied all six patches to for-next branch now.
> 
> ... and now I realized that it's conflicting with the latest Tegra234
> reset stuff on linux-next.
> 
> 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

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

  parent reply	other threads:[~2022-02-16 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  6:50 [PATCH v2 0/6] Add Tegra234 HDA support Mohan Kumar
2022-02-10  6:50 ` [PATCH v2 1/6] ALSA: hda/tegra: Add Tegra234 hda driver support Mohan Kumar
2022-02-10  6:50 ` [PATCH v2 2/6] ALSA: hda/tegra: Hardcode GCAP ISS value on T234 Mohan Kumar
2022-02-10  6:50 ` [PATCH v2 3/6] ALSA: hda/tegra: Update scratch reg. communication Mohan Kumar
2022-02-10  6:50 ` [PATCH v2 4/6] dt-bindings: Add HDA support for Tegra234 Mohan Kumar
2022-02-16  7:33   ` Mikko Perttunen
2022-02-10  6:50 ` [PATCH v2 5/6] dt-bindings: Document Tegra234 HDA support Mohan Kumar
2022-02-10  6:50 ` [PATCH v2 6/6] arm64: tegra: Add hda dts node for Tegra234 Mohan Kumar
2022-02-15 13:29 ` [PATCH v2 0/6] Add Tegra234 HDA support Takashi Iwai
2022-02-15 13:34   ` Takashi Iwai
2022-02-16  7:31     ` Mohan Kumar D
2022-02-16 14:23     ` Thierry Reding [this message]
2022-02-16 14:41       ` Takashi Iwai

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=Yg0I312RA5gh1Rra@orome \
    --to=thierry.reding@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=spujar@nvidia.com \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).