From: Aaron Conole <aconole@redhat.com>
To: John Romein <romein@astron.nl>
Cc: Elena Agostini <eagostini@nvidia.com>,
dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
David Marchand <dmarchan@redhat.com>
Subject: Re: DPDK patch
Date: Tue, 26 Sep 2023 11:04:19 -0400 [thread overview]
Message-ID: <f7tjzsdrn64.fsf@redhat.com> (raw)
In-Reply-To: <bbe34629-b425-7731-bfa4-97ad87550938@astron.nl> (John Romein's message of "Mon, 25 Sep 2023 21:16:32 +0200")
John Romein <romein@astron.nl> writes:
> Dear Elena, Aaron,
Hi John,
> I hope you had a nice time after the DPDK workshop.
>
> I was unable to solve the issues with our mailserver to submit a patch
> with git sendmail. So I created a pull request:
> https://github.com/DPDK/dpdk/pull/69
> @Elena, could you please handle the pull request? I will submit
> another pull request for the mempool_get_extmem optimization shortly.
Okay - we typically don't use pull requests. If you and others are are
okay, I can take the patches and repost them to the ML from the pull
requests with a note indicating such.
> Thanks, John
next prev parent reply other threads:[~2023-09-26 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 19:16 John Romein
2023-09-26 15:04 ` Aaron Conole [this message]
2023-09-26 15:07 ` John Romein
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=f7tjzsdrn64.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=dmarchan@redhat.com \
--cc=eagostini@nvidia.com \
--cc=romein@astron.nl \
--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).