From: Joshua Washington <joshwash@google.com>
To: Shreesh Adiga <16567adigashreesh@gmail.com>
Cc: Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>,
dev@dpdk.org
Subject: Re: [PATCH] net/gve: fix RSS hash endianness in DQO format
Date: Sat, 6 Jul 2024 17:33:22 -0700 [thread overview]
Message-ID: <CALuQH+U_zjEd5TJ7b7oB25FY37tySHyGfrFc_UFwLd0YUAdwfQ@mail.gmail.com> (raw)
In-Reply-To: <20240703133153.157661-1-16567adigashreesh@gmail.com>
Thank you for your contribution, Shreesh! Let's get this applied as a
stable fix so that it can be applied to 23.11 as well.
https://doc.dpdk.org/guides/contributing/patches.html, section "Patch
for Stable Releases" should have more detail for how this can be done.
> Bugzilla ID: 1441
Please add a "fixes" tag as well. For reference, this is the commit
which is being fixed: net/gve: support basic Rx data path for DQO.
Thanks!
next prev parent reply other threads:[~2024-07-07 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 13:31 Shreesh Adiga
2024-07-07 0:33 ` Joshua Washington [this message]
2024-07-07 2:53 ` Shreesh Adiga
2024-07-07 13:42 ` Ferruh Yigit
2024-07-07 22:42 ` 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=CALuQH+U_zjEd5TJ7b7oB25FY37tySHyGfrFc_UFwLd0YUAdwfQ@mail.gmail.com \
--to=joshwash@google.com \
--cc=16567adigashreesh@gmail.com \
--cc=dev@dpdk.org \
--cc=jeroendb@google.com \
--cc=rushilg@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).