linux-kernel - Re: linux-next: manual merge of the sound-asoc tree with the sound-current tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5h8rx758g3.wl-tiwai@suse.de>
Date:   Mon, 29 Nov 2021 15:43:08 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     Kai Vehmanen <kai.vehmanen@...ux.intel.com>
Cc:     Mark Brown <broonie@...nel.org>, Takashi Iwai <tiwai@...e.de>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Liam Girdwood <lgirdwood@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
Subject: Re: linux-next: manual merge of the sound-asoc tree with the sound-current tree

On Mon, 29 Nov 2021 15:29:36 +0100,
Kai Vehmanen wrote:
> 
> Hi,
> 
> On Mon, 29 Nov 2021, Mark Brown wrote:
> 
> > On Mon, Nov 29, 2021 at 10:23:07AM +0100, Takashi Iwai wrote:
> > 
> > > Mark, could you resolve in the latter branch?
> > 
> > I'll just leave them for now, Linus got angry about merging up fixes
> > just to resolve conflicts so if it's not an actual dependency...
> 
> the asoc for-5.17 branch does have all the needed changes and the 
> linux-next merged version seems ok. We've already sent many further 
> changes that touch this area of code to asoc for-5.17. Let me know if some 
> actions are needed to help.

The question is rather whether this discrepancy would cause a problem
for further developments.  If back-merging 5.16 stuff makes things
easier, it should be done so.  OTOH, if it's just for resolving the
conflict in the final tree, we can leave it.


thanks,

Takashi