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 C1412C4332F for ; Fri, 10 Dec 2021 09:58:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239788AbhLJKCG (ORCPT ); Fri, 10 Dec 2021 05:02:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49404 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239756AbhLJKCF (ORCPT ); Fri, 10 Dec 2021 05:02:05 -0500 Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8684FC061746 for ; Fri, 10 Dec 2021 01:58:30 -0800 (PST) Received: by mail-ed1-x535.google.com with SMTP id g14so27453221edb.8 for ; Fri, 10 Dec 2021 01:58:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=nduhBFxPbxmifYpnO0eOOP3C7nxBPTbeIwjsdCqiSCo=; b=ojvvj0K+k6NKnozWLW2tDWy91766MZb9YsUkZZD84yq8yaH1DnzCgRGc4zW9CR+Z3E 2vs+BSinUml6Qjyb0MbBrOgsHOui0a02cPy0cqrIUgGcPho1kK21Vv6AOKU4syfzyGr6 ZSM2KKARJ2O3WXBsrc+VrUfgJgi8GAHaVHe2HKB+OvOoTqxMHIykUz6SEjjyVYLDofUT 4tkWQHYJ8a7xdoQKOL1TGvS9bCMzyhfSxCNiEPqsSQMJYT0YND2DBanJfy4thrcjQpsv NGVyKnbVO76+lE4LNwOMA8eTPqYUhFTsWhY12krSk4lNc2nU/54euf2N4eePg1MzmHYj PSKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=nduhBFxPbxmifYpnO0eOOP3C7nxBPTbeIwjsdCqiSCo=; b=xBFMU4p9IItNQpK23FufD3qWIU77HhXRShX75rB2a+SIQy8uvzVoymSGZ0dpVdkOj9 PoChY2jKm48S3z7rfoR69IamhZNTGQxFvHiZZznq4s+3OLLa1tWkk1UPN1eWD6zUR615 TJu6zcLWxhNJJ0BUEexmFjqJnrpDksy6v6En+P/Wt1BkidOyaCGGjyKz6ouO3bA8IzQL 66+6pSF6KXnENqS3tZVzJCVxWLPXqoOIw33tPhRXnzKalgfqKKL+FVp8Fg9n337lxAPd BSpRkDnmYMKKxsK2iiCHr4TMfgQQ9hxam5X1PXBgsNFmWT2UTA2Qm6JZdXTJrbBttkLf gLEQ== X-Gm-Message-State: AOAM532z4H+5t66afnxv9qfs1klS9IuovsoGgV6Wwq5LCcuTJOCZrb9N Zaf8KxP1metnV6mqIl1n4eUeDrw1mHwwo77X66Y= X-Google-Smtp-Source: ABdhPJylHws71T7EEEhue6UdCGoV/k4VWRPPxYHA0zXkEHzMN0zoHH6zuGQNrntdBPyvVA4MsSkOUQ== X-Received: by 2002:a17:907:7f2a:: with SMTP id qf42mr23268059ejc.388.1639130308873; Fri, 10 Dec 2021 01:58:28 -0800 (PST) Received: from [192.168.178.33] (94.105.100.208.dyn.edpnet.net. [94.105.100.208]) by smtp.gmail.com with ESMTPSA id co10sm1129754edb.83.2021.12.10.01.58.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Dec 2021 01:58:28 -0800 (PST) Message-ID: Date: Fri, 10 Dec 2021 10:58:27 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH] selftests: mptcp: remove duplicate include in mptcp_inq.c Content-Language: en-GB To: cgel.zte@gmail.com, mathew.j.martineau@linux.intel.com Cc: davem@davemloft.net, kuba@kernel.org, shuah@kernel.org, netdev@vger.kernel.org, mptcp@lists.linux.dev, linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, Ye Guojin , ZealRobot References: <20211210071424.425773-1-ye.guojin@zte.com.cn> From: Matthieu Baerts In-Reply-To: <20211210071424.425773-1-ye.guojin@zte.com.cn> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ye, On 10/12/2021 08:14, cgel.zte@gmail.com wrote: > From: Ye Guojin > > 'sys/ioctl.h' included in 'mptcp_inq.c' is duplicated. Good catch, the modification looks good to me: Reviewed-by: Matthieu Baerts This patch is for "net-next" tree as it fixes an issue introduced by a patch only in this tree: Fixes: b51880568f20 ("selftests: mptcp: add inq test case") Regarding the commit message, please next time include the Fixes tag and mention for which tree it is for in the FAQ [1], e.g. [PATCH net-next]. @David/Jakub: do you prefer a v2 with these modifications or is it fine to apply this small patch directly in net-next tree? Cheers, Matt [1] https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html Please check the "How do I indicate which tree (net vs. net-next) my patch should be in?" section. -- Tessares | Belgium | Hybrid Access Solutions www.tessares.net