patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>, dev@dpdk.org
Cc: stable@dpdk.org, Joshua Washington <joshwash@google.com>
Subject: Re: [PATCH v2] net/gve: Fix TX/RX queue setup and stop
Date: Wed, 31 Jul 2024 14:02:56 +0100	[thread overview]
Message-ID: <88f9dca2-3441-42ca-b380-d4f8f01bd253@amd.com> (raw)
In-Reply-To: <1722403603-2399714-1-git-send-email-tathagat.dpdk@gmail.com>

On 7/31/2024 6:26 AM, Tathagat Priyadarshi wrote:
> The PR aims to update the TX/RQ queue setup/stop routines that are
> unique to DQO, so that they may be called for instances that use the
> DQO RDA format during dev start/stop
> 
> Fixes: b044845 ("net/gve: support queue start/stop")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
>

Moving Joshua's ack from other thread:

Acked-by: Joshua Washington <joshwash@google.com>

Applied to dpdk-next-net/main, thanks.


Please note, although I applied the fix to the next-net, probably it
won't able to make the v23.07 release, as we are already post -rc4
phase. In that case patch will be merged to main repo for next release.


And a few other operational notes:
- I have updated patch title and commit log slightly, please check the
updates. For next contribution, please run the
'./devtools/check-git-log.sh' tool

- Sending a new version of the patch, with same version tag is
confusing, also it will be confusing when tracing back from commit to
the mail list / patchwork later. So please increase version tag when a
new version sent.


Thanks,
ferruh

      reply	other threads:[~2024-07-31 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1721914264-2394611-1-git-send-email-tathagat.dpdk@gmail.com>
2024-07-31  5:26 ` Tathagat Priyadarshi
2024-07-31 13:02   ` Ferruh Yigit [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=88f9dca2-3441-42ca-b380-d4f8f01bd253@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=joshwash@google.com \
    --cc=stable@dpdk.org \
    --cc=tathagat.dpdk@gmail.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).