DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Stanisław Kardach" <kda@semihalf.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Frank Zhao <Frank.Zhao@starfivetech.com>,
	 Sam Grove <sam.grove@sifive.com>,
	"mw@semihalf.com" <mw@semihalf.com>,
	 "upstream@semihalf.com" <upstream@semihalf.com>, nd <nd@arm.com>,
	 Stephen Hemminger <stephen@networkplumber.org>,
	 "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	 "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [PATCH 1/1] test/ring: remove excessive inlining
Date: Wed, 11 May 2022 16:39:57 +0200	[thread overview]
Message-ID: <CALVGJWL69WvKAPxpjwSz_ug04F1jSt-oPLGBCHNOTHLDHnKngg@mail.gmail.com> (raw)
In-Reply-To: <DBAPR08MB5814A2D32DA177C1BE4FCDD798C99@DBAPR08MB5814.eurprd08.prod.outlook.com>

On Wed, May 11, 2022 at 1:24 AM Honnappa Nagarahalli
<Honnappa.Nagarahalli@arm.com> wrote:
<snip>
> Is there a bug report created for this? Is it possible to add a link to the bug report?
I have found a bug for a similar issue (with "if" conditional):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93062
I'll add it in v2.

  parent reply	other threads:[~2022-05-11 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:57 Stanislaw Kardach
2022-05-10 23:23 ` Honnappa Nagarahalli
2022-05-11  9:14   ` Bruce Richardson
2022-05-11 14:39   ` Stanisław Kardach [this message]
2022-05-11 15:07 ` [PATCH v2 " Stanislaw Kardach
2022-05-11 15:48   ` Bruce Richardson
2022-05-23 13:31     ` David Marchand
2022-05-11 16:51   ` Honnappa Nagarahalli
2022-05-19 22:50   ` Konstantin Ananyev

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=CALVGJWL69WvKAPxpjwSz_ug04F1jSt-oPLGBCHNOTHLDHnKngg@mail.gmail.com \
    --to=kda@semihalf.com \
    --cc=Frank.Zhao@starfivetech.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=mw@semihalf.com \
    --cc=nd@arm.com \
    --cc=sam.grove@sifive.com \
    --cc=stephen@networkplumber.org \
    --cc=upstream@semihalf.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).