DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Shreesh Adiga <16567adigashreesh@gmail.com>,
	Joshua Washington <joshwash@google.com>
Cc: Jeroen de Borst <jeroendb@google.com>,
	Rushil Gupta <rushilg@google.com>,
	 dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH] net/gve: fix RSS hash endianness in DQO format
Date: Sun, 7 Jul 2024 14:42:35 +0100	[thread overview]
Message-ID: <fdeebb3e-d0a7-4ec0-ab6f-18d2c37ee930@amd.com> (raw)
In-Reply-To: <CA+-x59Zr3QOKu==tUXbTMjtz--SfhHrnQXYpE0zaZaXbF6Ji+Q@mail.gmail.com>

On 7/7/2024 3:53 AM, Shreesh Adiga wrote:
> Thank you Joshua for your review and suggestions. 
> Appreciate the help with dpdk process.
> I've sent a new patch with "Fixes" tag to stable@dpdk.org
> <mailto:stable@dpdk.org>. 
> I'm not sure if same needs to be sent here to dev@dpdk.org
> <mailto:dev@dpdk.org> as well.
> Please let me know if I've missed anything.
> 
> 

I am copy/pasting from the stable mail list patch:

Bugzilla ID: 1441
Fixes: 45da16b5b181 ("net/gve: support basic Rx data path for DQO")
Cc: junfeng.guo@intel.com
Cc: stable@dpdk.org


You should send a fix to dev & stable mail list, with commit log has
'Fixes' & 'stable' tag.
Patch is first merged to main tree, tested and released. Later it is
backported to LTS release by LTS tree maintainers, this is when 'Fixes'
& 'stable' tags in commit log is used.

If a fix can't be backported to an LTS automatically, that is when a fix
need to be backported manually by its author to a specific LTS release
and sent only to stable mail list. It is not the case for this patch.

*Only* fixes merged and tested in the regular release are backported
(automatically or manually) to LTS trees. A fix can't exist only in LTS
release.


Briefly, expectation is send this fix both dev and stable mail list,
with commit log has 'Fixes' and 'stable' (Cc: stable@dpdk.org) tag.
No need to send a new version of this patch, I will use above data to
proceed with the patch.

  reply	other threads:[~2024-07-07 13:42 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
2024-07-07  2:53   ` Shreesh Adiga
2024-07-07 13:42     ` Ferruh Yigit [this message]
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=fdeebb3e-d0a7-4ec0-ab6f-18d2c37ee930@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=16567adigashreesh@gmail.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=jeroendb@google.com \
    --cc=joshwash@google.com \
    --cc=ktraynor@redhat.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).