From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"David Marchand" <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, "Onar Olsen" <onar.olsen@ericsson.com>,
<Honnappa.Nagarahalli@arm.com>, <nd@arm.com>,
<konstantin.ananyev@intel.com>, <stephen@networkplumber.org>,
<hofors@lysator.liu.se>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Ola Liljedahl" <ola.liljedahl@arm.com>
Subject: Recall: [PATCH v7] eal: add seqlock
Date: Sun, 15 May 2022 17:22:38 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D8706F@smartserver.smartshare.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 80 bytes --]
Morten Brørup would like to recall the message, "[PATCH v7] eal: add seqlock".
[-- Attachment #2: Type: text/html, Size: 318 bytes --]
reply other threads:[~2022-05-15 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=98CBD80474FA8B44BF855DF32C47DC35D8706F@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=hofors@lysator.liu.se \
--cc=konstantin.ananyev@intel.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=nd@arm.com \
--cc=ola.liljedahl@arm.com \
--cc=onar.olsen@ericsson.com \
--cc=stephen@networkplumber.org \
--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).