From mboxrd@z Thu Jan 1 00:00:00 1970 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 A19D0C46467 for ; Thu, 19 Jan 2023 14:32:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229686AbjASOck (ORCPT ); Thu, 19 Jan 2023 09:32:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50634 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231263AbjASOcR (ORCPT ); Thu, 19 Jan 2023 09:32:17 -0500 Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 044E88103B for ; Thu, 19 Jan 2023 06:30:43 -0800 (PST) Received: by mail-wm1-x335.google.com with SMTP id k16so1692406wms.2 for ; Thu, 19 Jan 2023 06:30:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=2Umd92wRNfvAofgDIf+r9yO6iFgRztRZ4IYJ8AlzHdY=; b=vkJOCCzoL8vjtTPGRMsoOw1R7mAXvOAuerYWRxBWXaMunEvMBJjX9QndCAb/cafgXt Wp7AkkYDAcaPRBYQ2VzjOWVN5wMoZwqSQeukFJm2XD2SjfcQjxuESHU2zwmh/1FcbtXJ OR5MMr6FO9bGoSKOuVuORlUSNlWpvJonbFssJ4ND0rStfsU754zN4PuUj9O8ONNIjh4a XtpkqnpVW9+jKKgKSW7R6dKH1iBsVvX0/s9opm2SOcUAbFbwYsgnVMH8XvKRL/D2Bxl+ wln/UUynFA/QaLNWDnaf5NjAcf474M7n22HbeVud8gC0gqsEEcvlanaQjOHrda0OhsBF 77EA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2Umd92wRNfvAofgDIf+r9yO6iFgRztRZ4IYJ8AlzHdY=; b=EjNfwb3Ow4slJmMfD2LBtyaKwSPFLI6F+ww3Zg4G9wdZ+RSLhqgLBHCcmje4Tk1khO 4jf9fruAHjhIWfrCl1E8TPO7Mtvh3DuMjyy5plq7v38Zc1tHEGrfSSTgLWJKPvB4B8pW HElT7DiMfOpTJjthjRCpg8jmJqzLezOI0/fBVFublmLQCFMQuKlL03GUTYFN5MTL7NIe yZ+Ev/r2JSBtLe7P3Btjndf3gkQqrgX++6k+Ix6HckIHUwQ+bkNiOCdWCiJSRjQYj5To pcuEma4Gbfe/Wy6X1yijw7x6Nov+P3nkj68E2ya7atvIL0YVsAJF1XI4xYfWLvL1qdXV wOSA== X-Gm-Message-State: AFqh2kqMiF3GQUhFwq6HHm8k0Qs4WrqAKFjB3vKgXfiicpiYAD45Rf7X rmNaJrwEcExfJIIhpgtbU6FRSg== X-Google-Smtp-Source: AMrXdXt/qRZqd3d5H5nKuT29rqnbZSUkbKuOzkuX9Eo+5Br+urhGdBlFyU95SdJu1GACPisSU9MB5A== X-Received: by 2002:a05:600c:601c:b0:3d9:ee01:60a4 with SMTP id az28-20020a05600c601c00b003d9ee0160a4mr10567478wmb.1.1674138641269; Thu, 19 Jan 2023 06:30:41 -0800 (PST) Received: from [192.168.0.15] (cpc76484-cwma10-2-0-cust274.7-3.cable.virginm.net. [82.31.201.19]) by smtp.gmail.com with ESMTPSA id o12-20020a05600c4fcc00b003daff80f16esm6836420wmq.27.2023.01.19.06.30.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Jan 2023 06:30:40 -0800 (PST) Message-ID: <000e333d-f6df-0d08-07a0-2e7056bb6792@linaro.org> Date: Thu, 19 Jan 2023 14:30:39 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: linux-next: manual merge of the net-next tree with the net tree Content-Language: en-US To: Stephen Rothwell , David Miller , Networking , Matthieu Baerts Cc: Alex Elder , Jakub Kicinski , Linux Kernel Mailing List , Linux Next Mailing List References: <20230119114125.5182c7ab@canb.auug.org.au> From: Caleb Connolly In-Reply-To: <20230119114125.5182c7ab@canb.auug.org.au> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/01/2023 00:41, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got conflicts in: > > drivers/net/ipa/ipa_interrupt.c > drivers/net/ipa/ipa_interrupt.h > > between commit: > > 9ec9b2a30853 ("net: ipa: disable ipa interrupt during suspend") > > from the net tree and commits: > > 8e461e1f092b ("net: ipa: introduce ipa_interrupt_enable()") > d50ed3558719 ("net: ipa: enable IPA interrupt handlers separate from registration") > > from the net-next tree. > > I fixed it up (see below) 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. > Hi all, sorry for the delayed response to this. If this is the same fixup in Matthieu's email [1] (which it appears to be), I can confirm that it's the correct fix here. I based the patch on master as it is a bug fix which we intend to backport, I should have mentioned the conflict with Alex's patch on -next, apologies for the miscommunication. -- Kind Regards, Caleb (they/them)