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 sta...@dpdk.org
> <mailto:sta...@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....@intel.com
Cc: sta...@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: sta...@dpdk.org) tag.
No need to send a new version of this patch, I will use above data to
proceed with the patch.
