From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by dpdk.org (Postfix) with ESMTP id 79E76160 for ; Mon, 8 Oct 2018 09:28:57 +0200 (CEST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 05FA4780061; Mon, 8 Oct 2018 07:28:55 +0000 (UTC) Received: from [192.168.38.17] (91.220.146.112) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 8 Oct 2018 08:28:50 +0100 To: Thomas Monjalon , CC: , , References: <20181007222554.4886-1-thomas@monjalon.net> <20181007222554.4886-5-thomas@monjalon.net> From: Andrew Rybchenko Message-ID: Date: Mon, 8 Oct 2018 10:28:08 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20181007222554.4886-5-thomas@monjalon.net> Content-Language: en-GB X-Originating-IP: [91.220.146.112] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24142.003 X-TM-AS-Result: No-12.728400-8.000000-10 X-TMASE-MatchedRID: eVEkOcJu0F4OwH4pD14DsPHkpkyUphL9QPCPzycuBFNaW2Ktn+I8/ic/ xZYu98DIQhFkA2f5DR6VY4Kd+WjBk294Ipa1otxo/LLJcbWWqygW40XiUkbrG9vpj5+dNlQvVhb DEH23DRNs/RCmt+jMBAbbwbvky5uPxBQfgZq+9aoAsHFAeQm1ar/I3arxTrvimHy7uaiMrL49WM jlh3FgOL5jdUER9zvLZrx0VP+xF3vyo11e4g8WXIb9ftid8kBcfMhjt3b5PP0Cdb5O7YWLhlHXx CnNdK1OL0FRNMjhhaWKgWXlQrdwn9J24xzpGcj5PlujdkswUwcH519/vRZuOUIjuk0uJKN9xTPN 0i7ijGH3aCtTBCBhl3k48PxckV+kTX7PJ/OU3vKDGx/OQ1GV8rHlqZYrZqdItVX2a1/ZsVg2d6m EnQBRa/WHbmzrJCnmebzJhnfyFQDae4FL/9TyIP++3a6IvkIJd/dDfECv4CDQvzDTnKcURwb08y HW++JczDpaN3fwjTM= X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--12.728400-8.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24142.003 X-MDID: 1538983737-g_fBMOU8Ua7A Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH 4/5] ethdev: remove deprecated attach/detach functions 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: Mon, 08 Oct 2018 07:28:57 -0000 On 10/8/18 1:25 AM, Thomas Monjalon wrote: > The hotplug attach/detach features are implemented in EAL layer. > There is a new ethdev iterator to retrieve ports from ethdev layer. > > As announced earlier, the (buggy) ethdev functions are now removed. > > Signed-off-by: Thomas Monjalon <...> > diff --git a/doc/guides/contributing/documentation.rst b/doc/guides/contributing/documentation.rst > index 097575ad7..063c8b6c4 100644 > --- a/doc/guides/contributing/documentation.rst > +++ b/doc/guides/contributing/documentation.rst > @@ -615,19 +615,14 @@ The following are some guidelines for use of Doxygen in the DPDK API documentati > .. code-block:: c > > /** > - * Attach a new Ethernet device specified by arguments. > - * > - * @param devargs > - * A pointer to a strings array describing the new device > - * to be attached. The strings should be a pci address like > - * `0000:01:00.0` or **virtual** device name like `net_pcap0`. > - * @param port_id > - * A pointer to a port identifier actually attached. > + * Try to take the lock. > * > + * @param sl > + * A pointer to the spinlock. > * @return > - * 0 on success and port_id is filled, negative on error. > + * 1 if the lock is successfully taken; 0 otherwise. > */ > - int rte_eth_dev_attach(const char *devargs, uint8_t *port_id); > + int rte_spinlock_trylock (rte_spinlock_t *sl); > > * Doxygen supports Markdown style syntax such as bold, italics, fixed width text and lists. > For example the second line in the ``devargs`` parameter in the previous example will be rendered as: I think it would be better if the hunk goes separately. It is really confusing in the changeset.