patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Devendra Singh Rawat <dsinghrawat@marvell.com>
To: Igor Russkikh <irusskikh@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Rasesh Mody <rmody@marvell.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 2/2] qede: make driver accept bigger rss tables
Date: Mon, 22 Mar 2021 05:22:46 +0000	[thread overview]
Message-ID: <CY4PR18MB14961B1C60D0E0B06582E164B6659@CY4PR18MB1496.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CY4PR1801MB18163D24A04A05E43FF22B57B7689@CY4PR1801MB1816.namprd18.prod.outlook.com>

Sure Igor, I will do that.

Thanks,
Devendra

> -----Original Message-----
> From: Igor Russkikh <irusskikh@marvell.com>
> Sent: Friday, March 19, 2021 3:18 PM
> To: Devendra Singh Rawat <dsinghrawat@marvell.com>; dev@dpdk.org
> Cc: Rasesh Mody <rmody@marvell.com>; stable@dpdk.org
> Subject: RE: [PATCH 2/2] qede: make driver accept bigger rss tables
> 
> 
> > IMO, it will be better if the log message also states that RSS key is trimmed to
> 'len' size.
> 
> Resent v2, thanks.
> 
> Devendra, please take these two patches into our internal codebase as well.
> 
> Igor

      reply	other threads:[~2021-03-22  5:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210221111637.31193-1-irusskikh@marvell.com>
2021-02-21 11:16 ` [dpdk-stable] [PATCH 1/2] qede: reduce trace verbosity level Igor Russkikh
2021-03-11  9:13   ` Devendra Singh Rawat
2021-02-21 11:16 ` [dpdk-stable] [PATCH 2/2] qede: make driver accept bigger rss tables Igor Russkikh
2021-03-08 19:02   ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
2021-03-11  9:28   ` [dpdk-stable] " Devendra Singh Rawat
2021-03-19  9:48     ` Igor Russkikh
2021-03-22  5:22       ` Devendra Singh Rawat [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=CY4PR18MB14961B1C60D0E0B06582E164B6659@CY4PR18MB1496.namprd18.prod.outlook.com \
    --to=dsinghrawat@marvell.com \
    --cc=dev@dpdk.org \
    --cc=irusskikh@marvell.com \
    --cc=rmody@marvell.com \
    --cc=stable@dpdk.org \
    /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).