DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	dev@dpdk.org, Aman Singh <aman.deep.singh@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Simei Su <simei.su@intel.com>, Wenjun Wu <wenjun1.wu@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Xiao Wang <xiao.w.wang@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Jiawen Wu <jiawenwu@trustnetic.com>,
	Jian Wang <jianwang@trustnetic.com>,
	david.marchand@redhat.com,
	Olivier MATZ <olivier.matz@dev.6wind.com>
Subject: Re: [PATCH] drivers: remove compile-time option for IEEE 1588
Date: Thu, 3 Oct 2024 12:12:36 -0700	[thread overview]
Message-ID: <20241003121236.5c56171d@hermes.local> (raw)
In-Reply-To: <d4cfff81-f6bb-4041-9414-68b39ccb30b6@amd.com>

On Wed, 17 Apr 2024 14:24:00 +0100
Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> > :) remove compile flag in 24.11 LTS.
> > 
> > But we may end up in same situation in 24.11, some drivers not being
> > ready, so we should merge this patch very early in the 24.11 to give
> > time to drivers to fix if they were not ready at that time.
> > 
> > Other option is merge this patch in 24.07, so that vendors which were
> > not ready can plan a fix for 24.11? Although enforcing an update by
> > breaking the driver is not best planning, it may be an efficient one.
> >  
> 
> Hi Thomas and et al. ,
> 
> Is is good time to merge this patch, there is enough time to fix
> potential issues in this release, what do you think?

Patch needs rebase if going into 24.11

  reply	other threads:[~2024-10-03 19:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 13:28 Thomas Monjalon
2023-06-23 14:00 ` Ferruh Yigit
2023-06-25 15:45   ` Thomas Monjalon
2023-11-02 21:13     ` Ferruh Yigit
2023-11-02 21:21       ` Ajit Khaparde
2023-11-02 22:17         ` Thomas Monjalon
2023-11-03  0:08           ` Ferruh Yigit
2024-04-17 13:24             ` Ferruh Yigit
2024-10-03 19:12               ` Stephen Hemminger [this message]
2024-10-03 22:36                 ` Ferruh Yigit

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=20241003121236.5c56171d@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=ajit.khaparde@broadcom.com \
    --cc=aman.deep.singh@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jianwang@trustnetic.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=olivier.matz@dev.6wind.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=sachin.saxena@nxp.com \
    --cc=simei.su@intel.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=thomas@monjalon.net \
    --cc=wenjun1.wu@intel.com \
    --cc=xiao.w.wang@intel.com \
    --cc=yuying.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).