From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 95B501B7C7 for ; Tue, 10 Apr 2018 15:19:33 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2018 06:19:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,432,1517904000"; d="scan'208";a="219251086" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.128]) ([10.237.220.128]) by fmsmga005.fm.intel.com with ESMTP; 10 Apr 2018 06:19:31 -0700 To: "Tosatti, Giovanni" , "dev@dpdk.org" References: <40ff3805d8a647f8bda4a386cc6a3987@bilemail2.empirix.com> From: "Burakov, Anatoly" Message-ID: Date: Tue, 10 Apr 2018 14:19:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <40ff3805d8a647f8bda4a386cc6a3987@bilemail2.empirix.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Add option to dpdk-devbind.py to restore kernel driver binding X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 13:19:34 -0000 On 10-Apr-18 11:55 AM, Tosatti, Giovanni wrote: > This patch adds a " --restore" option that will unbind all devices currently bound to DPDK PMDs back to the kernel driver. > > --- /opt/Perforce/gtosatti_centos/E-XMS/CSA-Mainline/Third-Party/dpdk/dpdk-16.07.orig/tools/dpdk-devbind.py > +++ /opt/Perforce/gtosatti_centos/E-XMS/CSA-Mainline/Third-Party/dpdk/dpdk-16.07/tools/dpdk-devbind.py > @@ -91,6 +91,9 @@ > -u, --unbind: Two other issues: 1) the header is also wrongly formatted. it should read something like: tools/devbind: add option to restore kernel driver binding 2) the patch does not apply. not only it appears to be generated not from git-send-email but reads as a diff, but it looks like it's generated against a very old version of DPDK. You might want to look at DPDK contribution guidelines: http://dpdk.org/doc/guides/contributing/patches.html Thanks for your effort so far! -- Thanks, Anatoly