From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Ian Stokes <ian.stokes@intel.com>, dev@dpdk.org
Subject: Re: [RFC] net/ice: Update base code with latest snapshot.
Date: Wed, 01 May 2024 14:08:58 +0200 [thread overview]
Message-ID: <4661408.CvnuH1ECHv@thomas> (raw)
In-Reply-To: <ZjIF_k6VTzK93qgb@bricha3-mobl1.ger.corp.intel.com>
01/05/2024 11:06, Bruce Richardson:
> On Wed, May 01, 2024 at 10:19:54AM +0200, Thomas Monjalon wrote:
> > Hello Ian,
> >
> > In general, base drivers are updated with multiple commits, one per feature.
> > It helps tracking the changes.
> >
> > Please would it be possible to split?
> >
>
> Hi Thomas,
>
> yes, that is very much the intention. As Ian states in his last line, we
> sent this as an RFC to a) flag that the series is coming in future, and b)
> have an initial CI run done, while we work in parallel on splitting the
> code changes into a more meaningful series of commits. Given the scope of
> the changes we didn't have time to do the split yet, but wanted to get an
> inital RFC to the list.
OK thanks, I didn't pay enough attention to the last words.
> > PS: look like you are not registered in the mailing list,
> > this patch was in the moderation queue.
> >
> >
> > 30/04/2024 17:40, Ian Stokes:
> > > The purpose of this patch is to update shared code for the ice driver.
> > > This patch not only contains the updated base code files but also the
> > > required changes within the DPDK code base to enable compilation and
> > > basic functionality. This is with a view to allow further regression
> > > testing while a final patch series is generated that correctly splits
> > > the code changes into an expected manner.
> > >
> > > Signed-off-by: Ian Stokes <ian.stokes@intel.com>
prev parent reply other threads:[~2024-05-01 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240430154014.1026-1-ian.stokes@intel.com>
2024-05-01 8:19 ` [RFC] net/ice: Update base code with latest snapshot Thomas Monjalon
2024-05-01 9:06 ` Bruce Richardson
2024-05-01 12:08 ` Thomas Monjalon [this message]
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=4661408.CvnuH1ECHv@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@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 read-only IMAP folder(s) and NNTP newsgroup(s).