Received: by 10.223.185.116 with SMTP id b49csp2283594wrg; Thu, 22 Feb 2018 11:05:32 -0800 (PST) X-Google-Smtp-Source: AH8x225wIqbXzUhVJ0M/yTjxn9HaY7hiUII+46yM4ulee3gBj22gRIl2LHwE61YeKHHIXKEJOZ1w X-Received: by 10.98.72.204 with SMTP id q73mr7935024pfi.48.1519326332774; Thu, 22 Feb 2018 11:05:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519326332; cv=none; d=google.com; s=arc-20160816; b=eH4VsjYR5ytClGs0AW4CAoLemso5Mn9jAlt3tPqukUtpgL8Md+i5mLiIfo5Xtgtbc3 wwCjOuXUdI+p9iJ2EK3NqotYmAOwh7EvFBeCC0KdTNJgER06rlJy/Di41hjf9ufhOGRT O6u8q9FVOEkn9FfcL5s69NVyCVpzJaUL1wDFVHQVO41aHowtJfGekX5EZd/69XxS9XkG S5d8XbBGY8sOR67o0B6WhFN3ccGW8waFXSCpidBsYDCldTbyE2i9w3fppjwoLtUh/8/X XICbMnf9fNBdnxlM7jsXlA+ZnJurlRoeQSvrgo17TH91uPNDMqWqZtV3iw9+r63Y4uz0 QgbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=Mgapi2j8+/evqdzdny2uUT/AINit87hpBNmB45g9dhI=; b=b1zu2v4QbaNP8ETq6e0gshi+DCUcYg7uC1MLIiHY7B1B1lZYc92CuCfm41wb98Y5zO 9NZXgnmZ22kaanqkokz1kRHvBf2lIVF6zK/kkHH36PS6ZiDYfknkkfmfxqQP+qAZh+CD znDz8AxF9BIgdA49ESHslLFi9lgb/9lvkspl++3iBfM3pvM9HTint6tj0uC980W1TpiA VNjpoLG5MnpifOBBQpkwBHgzNuFNkmgt3KC4jsP2MjpBBSpeZAXe1vXh7MmyRZkbpCgu aAPiyZ1pyLPsUJzFjUjc/P17dF2O3xuMzA1ItcsLpfRk5RE4YM8us2E27bhfZNULmIqs VKFA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o16si389556pgd.125.2018.02.22.11.05.18; Thu, 22 Feb 2018 11:05:32 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751327AbeBVTEc convert rfc822-to-8bit (ORCPT + 99 others); Thu, 22 Feb 2018 14:04:32 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:50542 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750776AbeBVTEb (ORCPT ); Thu, 22 Feb 2018 14:04:31 -0500 Received: from localhost (67.110.78.66.ptr.us.xo.net [67.110.78.66]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 98F4513F03480; Thu, 22 Feb 2018 11:04:30 -0800 (PST) Date: Thu, 22 Feb 2018 14:04:29 -0500 (EST) Message-Id: <20180222.140429.928803762162231850.davem@davemloft.net> To: dudenis2000@yahoo.ca Cc: khc@pm.waw.pl, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Carrier detect ok, don't turn off negotiation From: David Miller In-Reply-To: <1603547691.2507241.1519184131708@mail.yahoo.com> References: <20180206.102943.1688399898359622454.davem@davemloft.net> <2005408285.4065183.1517935842178@mail.yahoo.com> <1603547691.2507241.1519184131708@mail.yahoo.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 22 Feb 2018 11:04:30 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Denis Du Date: Wed, 21 Feb 2018 03:35:31 +0000 (UTC) > How? is your thinking about this patch? I cannot apply a patch which has been corrupted by your email client like this. Please send it properly again, plain ASCII text, and no trasnformations by your email client. You should send the patch to yourself and try to apply the patch you receive, do not send to the list until you can pass the test properly. Do not use attachments to fix this problem, the patch must be inline after your commit message and signoffs. Please read Documentation/process/submitting-patches.rst and Documentation/process/email-clients.rsDt for more information. Thank you.