From: Bruce Richardson <bruce.richardson@intel.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] event/sw: remove obsolete comment
Date: Thu, 14 Sep 2023 11:29:12 +0100 [thread overview]
Message-ID: <ZQLgeMOJGxARoGB6@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <PH8PR11MB6803B42BEDD53760E6DC96C9D7F7A@PH8PR11MB6803.namprd11.prod.outlook.com>
On Thu, Sep 14, 2023 at 11:10:17AM +0100, Van Haaren, Harry wrote:
> > -----Original Message-----
> > From: Richardson, Bruce <bruce.richardson@intel.com>
> > Sent: Thursday, September 14, 2023 10:38 AM
> > To: dev@dpdk.org
> > Cc: Van Haaren, Harry <harry.van.haaren@intel.com>; Richardson, Bruce
> > <bruce.richardson@intel.com>; stable@dpdk.org
> > Subject: [PATCH] event/sw: remove obsolete comment
> >
> > Code that the comment refers to was previously removed, but the
> > comment remained.
> >
> > Fixes: dca926ca9faa ("event/sw: use dynamically-sized IQs")
> > Cc: stable@dpdk.org
>
> Do we want to backport this? It's a code-level change, that doesn't really "fix" any issue.
> I'm fine with it being backported to stables, or skipped.
>
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
I'd take the view that since backporting is going to be entirely harmless,
and it does fix the code for anyone trying to read it, we might as well do so.
next prev parent reply other threads:[~2023-09-14 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 9:37 Bruce Richardson
2023-09-14 10:10 ` Van Haaren, Harry
2023-09-14 10:29 ` Bruce Richardson [this message]
2023-09-15 15:12 ` Stephen Hemminger
2023-09-19 14:05 ` Jerin Jacob
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=ZQLgeMOJGxARoGB6@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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).