From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EF219A054A; Tue, 7 Jun 2022 14:42:58 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9B2B44021D; Tue, 7 Jun 2022 14:42:58 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id E3D0D40156 for ; Tue, 7 Jun 2022 14:42:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654605776; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6SIA8Brx7ruEQ2VzHKLyXB4sDic0oXrHbjgLOwI6fEc=; b=cWnviq2H0cuf46tQaXnVB2dNYKHKcME9otZ1LUg/CbEX3yqH9Or/sIAGLBqtArJ+2UNGUX eijaczJEfYnzoh/A8D2Ma3MpFcdw0nHF7f00RCBtkLEewdBV+R9zgDQ+Nfqhb95gLrhz9D ZPEGMwP4Xob3kR0hzU++M6+wRs7sCAY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-216-jCqYz97rP4q2JddWBl5aIw-1; Tue, 07 Jun 2022 08:42:53 -0400 X-MC-Unique: jCqYz97rP4q2JddWBl5aIw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id CBC97185A7A4; Tue, 7 Jun 2022 12:42:52 +0000 (UTC) Received: from [10.39.208.28] (unknown [10.39.208.28]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 14E22C27E98; Tue, 7 Jun 2022 12:42:49 +0000 (UTC) Message-ID: <9f995dde-738e-6c56-c4ef-41c9ad0f4926@redhat.com> Date: Tue, 7 Jun 2022 14:42:48 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v1] bbdev: add device status info To: Stephen Hemminger , Nicolas Chautru Cc: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com, hemant.agrawal@nxp.com, hernan.vargas@intel.com References: <1654555808-218770-1-git-send-email-nicolas.chautru@intel.com> <1654555808-218770-2-git-send-email-nicolas.chautru@intel.com> <20220606170906.6265c598@hermes.local> From: Maxime Coquelin In-Reply-To: <20220606170906.6265c598@hermes.local> X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Stephen, On 6/7/22 02:09, Stephen Hemminger wrote: > On Mon, 6 Jun 2022 15:50:08 -0700 > Nicolas Chautru wrote: > >> @@ -298,6 +313,8 @@ struct rte_bbdev_driver_info { >> const struct rte_bbdev_op_cap *capabilities; >> /** Device cpu_flag requirements */ >> const enum rte_cpu_flag_t *cpu_flag_reqs; >> + /** Device Status */ >> + enum rte_bbdev_device_status device_status; >> }; >> > > This ends up being an ABI breakage, can't change a struct like that > until 22.11 release. > Indeed, but Nicolas mentioned in the cover-letter that the patch targets v22.11; not this release. However, a deprecation notice should be sent for v22.07 if it hasn't been done yet. Maxime