All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com,
	hemant.agrawal@nxp.com, hernan.vargas@intel.com
Subject: Re: [PATCH v1] bbdev: add device status info
Date: Tue, 7 Jun 2022 14:42:48 +0200	[thread overview]
Message-ID: <9f995dde-738e-6c56-c4ef-41c9ad0f4926@redhat.com> (raw)
In-Reply-To: <20220606170906.6265c598@hermes.local>

Hi Stephen,

On 6/7/22 02:09, Stephen Hemminger wrote:
> On Mon,  6 Jun 2022 15:50:08 -0700
> Nicolas Chautru <nicolas.chautru@intel.com> 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


  reply	other threads:[~2022-06-07 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 22:50 [PATCH v1] bbdev: add device status info Nicolas Chautru
2022-06-06 22:50 ` Nicolas Chautru
2022-06-07  0:09   ` Stephen Hemminger
2022-06-07 12:42     ` Maxime Coquelin [this message]
2022-06-07 15:44       ` Chautru, Nicolas
2022-06-07 16:20         ` Maxime Coquelin
2022-06-07 16:42           ` Stephen Hemminger
2022-06-08 22:44             ` Chautru, Nicolas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9f995dde-738e-6c56-c4ef-41c9ad0f4926@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=trix@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.