DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Joshua Washington <joshwash@google.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: Jeroen de Borst <jeroendb@google.com>,
	dev@dpdk.org,  Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH] net/gve: remove gve-specific PCI revision ID macros
Date: Wed, 14 May 2025 10:43:25 +0200	[thread overview]
Message-ID: <CAJFAV8yubQF_YJPGBQgs2oBzatFn4_D7CBWm92Ubtc=SVqu0-A@mail.gmail.com> (raw)
In-Reply-To: <CALuQH+XJqOAetnTO0b_t55Wf1Qn38dQSZvgj1rf=pTKja6ozyw@mail.gmail.com>

Hello,

Thanks for the cleanup.

On Wed, May 14, 2025 at 2:46 AM Joshua Washington <joshwash@google.com> wrote:
>
> Patch doesn't apply to the main branch of dpdk-next-net:
> https://mails.dpdk.org/archives/test-report/2025-May/877522.html
>
> It seems like the diffbase patch only exists in the for-main branch.
> When is for-main expected to be merged into main, and should we be
> building against for-main or main? Similarly, what should this
> compilation test build against?

Stephen is out for some time (until next week?).

Thomas may pull next-net soon.
(@Thomas it would be great if this additional change was squashed in
96a1290b6258 ("net/gve: support for gVNIC PCI revision 1 and later")
while pulling.)
But otherwise this cleanup can be merged after.

In any case, for net drivers update, please continue basing your work
on next-net.

Thanks.

-- 
David Marchand


      reply	other threads:[~2025-05-14  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 23:53 Joshua Washington
2025-05-14  0:46 ` Joshua Washington
2025-05-14  8:43   ` David Marchand [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='CAJFAV8yubQF_YJPGBQgs2oBzatFn4_D7CBWm92Ubtc=SVqu0-A@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jeroendb@google.com \
    --cc=joshwash@google.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).