From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Jie Yang <yang.jie@linux.intel.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH 0/3] ALSA: hda: bus cleanup
Date: Thu, 08 Aug 2019 16:45:09 +0200 [thread overview]
Message-ID: <s5hr25vhg22.wl-tiwai@suse.de> (raw)
In-Reply-To: <ae7d32fe-a279-8309-2370-1832edcce413@linux.intel.com>
On Thu, 08 Aug 2019 16:23:40 +0200,
Pierre-Louis Bossart wrote:
>
> One request from me since I am lazy: could we somehow merge branches
> between you / Mark since at the moment we have two sets of conflicts
> (NHLT and this one). We test all the upstream changes on hardware as
> soon as we can, and manual conflict resolution makes it slower/more
> error prone.
I don't mind who actually merges. I'm going to push out my topic
branch once after gathering enough Ack's. Then Mark can pull it into
his tree (as well as topic/hda-dmic branch).
Or if Mark can give me the branch, I can pull into my for-next
branch, too. Basically my for-next branch is persistent and not
rebased, so you can work on it once when set.
Mark, just let me know your preference.
thanks,
Takashi
next prev parent reply other threads:[~2019-08-08 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 9:57 [PATCH 0/3] ALSA: hda: bus cleanup Takashi Iwai
2019-08-08 9:57 ` [PATCH 1/3] ALSA: hda: Remove page allocation redirection Takashi Iwai
2019-08-08 9:57 ` [PATCH 2/3] ALSA: hda: Direct MMIO accesses Takashi Iwai
2019-08-08 9:57 ` [PATCH 3/3] ASoC: SOF: Intel: Initialize hdaudio bus properly Takashi Iwai
2019-08-08 13:13 ` Mark Brown
2019-08-08 14:23 ` [PATCH 0/3] ALSA: hda: bus cleanup Pierre-Louis Bossart
2019-08-08 14:45 ` Takashi Iwai [this message]
2019-08-08 19:03 ` Mark Brown
2019-08-08 20:38 ` Takashi Iwai
2019-08-08 21:33 ` Mark Brown
2019-08-08 22:22 ` Mark Brown
2019-08-09 5:58 ` Takashi Iwai
2019-08-09 11:38 ` 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=s5hr25vhg22.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=thierry.reding@gmail.com \
--cc=yang.jie@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox