DPDK patches and discussions
 help / color / mirror / Atom feed
From: Joshua Washington <joshwash@google.com>
To: Jeroen de Borst <jeroendb@google.com>,
	Joshua Washington <joshwash@google.com>
Cc: dev@dpdk.org, David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] net/gve: remove gve-specific PCI revision ID macros
Date: Tue, 13 May 2025 17:46:27 -0700	[thread overview]
Message-ID: <CALuQH+XJqOAetnTO0b_t55Wf1Qn38dQSZvgj1rf=pTKja6ozyw@mail.gmail.com> (raw)
In-Reply-To: <20250513235308.2200865-1-joshwash@google.com>

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?

Thanks,
Josh

      reply	other threads:[~2025-05-14  0:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 23:53 Joshua Washington
2025-05-14  0:46 ` Joshua Washington [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='CALuQH+XJqOAetnTO0b_t55Wf1Qn38dQSZvgj1rf=pTKja6ozyw@mail.gmail.com' \
    --to=joshwash@google.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jeroendb@google.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).