Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp5175313pxv; Wed, 28 Jul 2021 05:07:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzoIbiWRpr3SHcyLyYusud1M/1M1nGhHk06s+e4NjE4z6H1/bDmWRTa/SWp1ssob3X+VI9+ X-Received: by 2002:a05:6402:c01:: with SMTP id co1mr3115947edb.287.1627474064852; Wed, 28 Jul 2021 05:07:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627474064; cv=none; d=google.com; s=arc-20160816; b=BFQZFxUCkIH+X/TnadQSF5tNId7Zt9X3D/Sh4pZsEsZh9kv507RzqxAQ4GXH9864LV KWrf6IbAOQaePHouJmTuj+U0xTbtSzyFiFerNIJ5FQ0JRFzcg/9buDZ+dmLtTdRjxPqI WJGwyR6mDpf/xXBNtU2rZWTN2cm21m2ukB0dQCOLgijwDGfooyoLQo1NwdmVpFuAW/Nt xCwC63zhu3ex5OyFrfd0upmhg9ZIUMRxTySIdYQqe9EdPpVML7XW1i3xxMHN8pDsSU5u rXk5MTOq3KgDhm0+BJCzdx5aC1AvBmUC66CRYaFGFCp+2PEh7FxznqjMxB0dJ2STaAkK 6mqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=nKK33wPrB0t5n8Odouj9O4JCxZR7nWF9JrMaXPJfwgM=; b=NCATCu6xfRYUxu/dLMvmkhTqAw4yMnklB92AXLlCikMSdCBLD6q3QGikpeo+pQEEMe sa0w6EU26e+E1QbFhh2zanA+KAJix4eaTVMX2vwZkWPsj3szvITH6G20aHqchv6FpSnh Rk0bzvqHCFOTmdjCDr6/w5UDP6QTbYUk/Jumxp7d0jf5gCVJMijYsDvhOND/Ub77T0lA DaAkakbEHH9Ot5DW453txNY+YQI9sDQlkd7xt19U9wwv2okfttLeIH+RoUCaF03auKG2 3MZuguRvLOzBwB1WQVCM65xBH6DZGY66lKjy+LIYffdTNpUacct+2KtIqBraugY4Boaz yBZQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b7si5594451edr.480.2021.07.28.05.07.20; Wed, 28 Jul 2021 05:07:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234872AbhG1MEN (ORCPT + 99 others); Wed, 28 Jul 2021 08:04:13 -0400 Received: from cmccmta1.chinamobile.com ([221.176.66.79]:44165 "EHLO cmccmta1.chinamobile.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234882AbhG1MEJ (ORCPT ); Wed, 28 Jul 2021 08:04:09 -0400 Received: from spf.mail.chinamobile.com (unknown[172.16.121.11]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee161014794d62-a754f; Wed, 28 Jul 2021 20:03:32 +0800 (CST) X-RM-TRANSID: 2ee161014794d62-a754f X-RM-TagInfo: emlType=0 X-RM-SPAM-FLAG: 00000000 Received: from [192.168.26.114] (unknown[10.42.68.12]) by rmsmtp-syy-appsvr06-12006 (RichMail) with SMTP id 2ee661014793ec2-c63e1; Wed, 28 Jul 2021 20:03:32 +0800 (CST) X-RM-TRANSID: 2ee661014793ec2-c63e1 Subject: Re: linux-next: manual merge of the net-next tree with the net tree To: Mark Brown , David Miller , Networking Cc: Linux Kernel Mailing List , Linux Next Mailing List , wengjianfeng References: <20210728105423.1064-1-broonie@kernel.org> From: tangbin Message-ID: <72a0bb43-3c60-7958-062b-c77037d9e725@cmss.chinamobile.com> Date: Wed, 28 Jul 2021 20:03:58 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20210728105423.1064-1-broonie@kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Mark: On 2021/7/28 18:54, Mark Brown wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > drivers/nfc/s3fwrn5/firmware.c > > between commit: > > 801e541c79bb ("nfc: s3fwrn5: fix undefined parameter values in dev_err()") Yesterday, I have send this patch to fix the problem. And nathan proposed another way to fix this problem, so I send v2 for maintainer today. And waiting for the result. Thanks Tang Bin > > from the net tree and commit: > > a0302ff5906a ("nfc: s3fwrn5: remove unnecessary label") > > 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. > > diff --cc drivers/nfc/s3fwrn5/firmware.c > index 1340fab9565e,1421ffd46d9a..000000000000 > --- a/drivers/nfc/s3fwrn5/firmware.c > +++ b/drivers/nfc/s3fwrn5/firmware.c > @@@ -421,10 -421,9 +421,9 @@@ int s3fwrn5_fw_download(struct s3fwrn5_ > > tfm = crypto_alloc_shash("sha1", 0, 0); > if (IS_ERR(tfm)) { > - ret = PTR_ERR(tfm); > dev_err(&fw_info->ndev->nfc_dev->dev, > - "Cannot allocate shash (code=%d)\n", ret); > + "Cannot allocate shash (code=%ld)\n", PTR_ERR(tfm)); > - goto out; > + return PTR_ERR(tfm); > } > > ret = crypto_shash_tfm_digest(tfm, fw->image, image_size, hash_data);