From: Stephen Hemminger <stephen@networkplumber.org>
To: Joshua Washington <joshwash@google.com>
Cc: Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>,
Xiaoyun Li <xiaoyun.li@intel.com>,
dev@dpdk.org, stable@dpdk.org,
Praveen Kaligineedi <pkaligineedi@google.com>
Subject: Re: [PATCH v4] net/gve: allocate RX QPL pages using malloc
Date: Thu, 9 Jan 2025 14:14:06 -0800 [thread overview]
Message-ID: <20250109141406.29f8119b@fedora> (raw)
In-Reply-To: <CALuQH+WkxmXH4-SSeRowB_y6fwajom2tpiO2HH5iG5uVfzFqwQ@mail.gmail.com>
On Thu, 9 Jan 2025 12:05:43 -0800
Joshua Washington <joshwash@google.com> wrote:
> Hello,
>
> I wish for this fix to be backported to stable release 22.11 and 23.11
> for DPDK. However, the patch as it is does not apply cleanly to either
> release. What is the recommended way to include this patch in older
> releases of DPDK? Should I create separate stable backport patches
> that apply cleanly to each of the stable releases? Or will this issue
> be resolved once stable maintainers attempt to apply the patch on
> older releases?
>
> Thanks,
> Josh
1. You must wait until it accepted in to main branch for an upcoming release.
2. Make sure it you add Fixes tag and Cc stable@dpdk.org
The stable maintainers pick it up from there.
3. If patch does not apply cleanly, they send out a "help with backporting" mail
before release with instructions.
prev parent reply other threads:[~2025-01-09 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250107190258.2107909-1-joshwash@google.com>
2025-01-09 19:46 ` Joshua Washington
2025-01-09 20:05 ` Joshua Washington
2025-01-09 22:14 ` Stephen Hemminger [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=20250109141406.29f8119b@fedora \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=stable@dpdk.org \
--cc=xiaoyun.li@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).