DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Suresh Narayane, Harshad" <harshad.suresh.narayane@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] pipeline: fix comparison
Date: Thu, 16 Jun 2022 09:17:04 +0000	[thread overview]
Message-ID: <DM8PR11MB5670F6D633608C692B1FE2F7EBAC9@DM8PR11MB5670.namprd11.prod.outlook.com> (raw)
In-Reply-To: <22804801.EfDdHjke4D@thomas>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, June 15, 2022 8:06 PM
> To: Suresh Narayane, Harshad <harshad.suresh.narayane@intel.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH] pipeline: fix comparison
> 
> 13/06/2022 13:52, Cristian Dumitrescu:
> > From: Harshad Narayane <harshad.suresh.narayane@intel.com>
> >
> > Fix comparison used to check against the maximum number of learner
> > table timeouts.
> >
> > Fixes: e2ecc53582fb ("pipeline: improve learner table timers")
> 
> The title is not informative about what is fixed.
> Please give a bit of scope so people experiencing an issue
> will know it is fixed.
> You can at least give the words "learner table timers"
> and maybe "check of maximum".
> 
> 

Thanks, Thomas, done in V2 just sent out:
https://patches.dpdk.org/project/dpdk/list/?series=23562

Regards,
Cristian

  reply	other threads:[~2022-06-16  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 11:52 Cristian Dumitrescu
2022-06-15 19:06 ` Thomas Monjalon
2022-06-16  9:17   ` Dumitrescu, Cristian [this message]
2022-06-16  9:14 ` [PATCH V2] pipeline: fix check against max number of learner table timeouts Cristian Dumitrescu
2022-06-20 14:07   ` Thomas Monjalon

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=DM8PR11MB5670F6D633608C692B1FE2F7EBAC9@DM8PR11MB5670.namprd11.prod.outlook.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=harshad.suresh.narayane@intel.com \
    --cc=thomas@monjalon.net \
    /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).