Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8E6CCC433EF for ; Mon, 29 Nov 2021 09:25:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244166AbhK2J20 (ORCPT ); Mon, 29 Nov 2021 04:28:26 -0500 Received: from smtp-out1.suse.de ([195.135.220.28]:42260 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232635AbhK2J0Z (ORCPT ); Mon, 29 Nov 2021 04:26:25 -0500 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id 99E28212C0; Mon, 29 Nov 2021 09:23:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1638177787; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FltWFYbNMlP6+ic6w15o8tUFEORPdPUdpEp6nj6Gg/Q=; b=dwoiXUQlLaC3GwkyNh04FeUPv0pyikVgjilLlvaPaf38xFp+Diz3QnxGNcvy55iWEOYCUq FeL8S2x5WoStqx/EpTy6/UluHr04e57u7IqUCXVZSArbjj9WbcyB9BcxpkRcuqRpXwsq// sEbBH92Kpon8mPfvTyAzSGVuNSYTmJc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1638177787; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FltWFYbNMlP6+ic6w15o8tUFEORPdPUdpEp6nj6Gg/Q=; b=6dPicQ/aSjnTzbR9w5IoDVOyROq9LFwLd5BnOdHbHWCHkLRmxUO9UNXz4SHCOpxJf9IcsA eiFHrgOBDEMU/kCQ== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id 83E6DA3B81; Mon, 29 Nov 2021 09:23:07 +0000 (UTC) Date: Mon, 29 Nov 2021 10:23:07 +0100 Message-ID: From: Takashi Iwai To: Mark Brown Cc: Stephen Rothwell , Liam Girdwood , Takashi Iwai , Kai Vehmanen , Linux Kernel Mailing List , Linux Next Mailing List , Ranjani Sridharan Subject: Re: linux-next: manual merge of the sound-asoc tree with the sound-current tree In-Reply-To: <20211129113554.59416109@canb.auug.org.au> References: <20211129113554.59416109@canb.auug.org.au> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 29 Nov 2021 01:35:54 +0100, Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the sound-asoc tree got a conflict in: > > sound/soc/sof/intel/hda.c > > between commit: > > 86f74ba3fef5 ("ASoC: SOF: hda: reset DAI widget before reconfiguring it") > > from the sound-current tree and commit: > > a0f84dfb3f6d ("ASoC: SOF: IPC: dai: Expand DAI_CONFIG IPC flags") > > from the sound-asoc tree. > > I fixed it up (I just used the latter version) and can carry the fix as > necessary. This is now fixed as far as linux-next is concerned, but any > non trivial conflicts should be mentioned to your upstream maintainer > when your tree is submitted for merging. You may also want to consider > cooperating with the maintainer of the conflicting tree to minimise any > particularly complex conflicts. Both are from ASoC tree, while the former landed in my sound git tree for-linus branch recently. Mark, could you resolve in the latter branch? thanks, Takashi