From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, "Anatoly Burakov" <anatoly.burakov@intel.com>
Subject: Re: [PATCH] eal: remove return from functions declared void return type
Date: Tue, 17 Oct 2023 12:29:31 -0700 [thread overview]
Message-ID: <20231017192931.GA24204@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <CAJvnSUDaz-_Ot1+Ldm=V+WD5Ky85m1JfCwrrBsfZf-JO8DRdOQ@mail.gmail.com>
On Tue, Oct 17, 2023 at 01:51:39PM -0400, Patrick Robb wrote:
> Recheck-request: iol-broadcom-Functional
>
> Sorry, this series was affected by an infra failure today.
No big deal, I haven't got a lot of concerns over the correctness of
this particular series. :)
next prev parent reply other threads:[~2023-10-17 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 13:03 Tyler Retzlaff
2023-10-17 13:14 ` Morten Brørup
2023-10-17 17:51 ` Patrick Robb
2023-10-17 19:29 ` Tyler Retzlaff [this message]
2023-10-26 8:42 ` David Marchand
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=20231017192931.GA24204@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=probb@iol.unh.edu \
/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).