From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Robert Sanford <rsanford2@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/3] timer: fix rte_timer_reset
Date: Wed, 25 Feb 2015 12:09:32 +0100 [thread overview]
Message-ID: <11399530.HyKjJqreJb@xps13> (raw)
In-Reply-To: <CA+cr1crDcQcdtJc9zaHbCL9DG40aV3a3ZF_fnNBx2h3WZP-quQ@mail.gmail.com>
2015-02-25 06:02, Robert Sanford:
> Hi Thomas,
>
> Yes, I'm interested in becoming a maintainer of rte_timer. What are the
> responsibilities?
It means we know someone who can answer our questions about rte_timer.
Having you email in the MAINTAINERS file helps to CC you.
And we expect from the maintainer he tried to review patches for its part.
But reviews may be done by someone else.
In general, technical review from the maintainer is more trustable.
If you are still interested, please drop a patch like this one:
http://dpdk.org/browse/dpdk/commit/?id=a7d7ece480093
next prev parent reply other threads:[~2015-02-25 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 20:42 [dpdk-dev] [RFC PATCH] rte_timer: Fix rte_timer_reset return value rsanford2
2015-02-06 11:10 ` Olivier MATZ
2015-02-06 17:26 ` Robert Sanford
2015-02-08 10:53 ` Olivier MATZ
2015-02-25 4:09 ` [dpdk-dev] [PATCH v2 0/3] timer: fix rte_timer_reset Robert Sanford
2015-02-25 8:58 ` Olivier MATZ
2015-02-25 9:46 ` Thomas Monjalon
2015-02-25 11:02 ` Robert Sanford
2015-02-25 11:09 ` Thomas Monjalon [this message]
2015-02-25 11:16 ` Bruce Richardson
2015-02-25 13:34 ` Robert Sanford
2015-02-25 4:09 ` [dpdk-dev] [PATCH v2 1/3] timer: pause in rte_timer_reset_sync Robert Sanford
2015-02-25 4:09 ` [dpdk-dev] [PATCH v2 2/3] timer: fix stress test on multiple runs Robert Sanford
2015-02-25 4:09 ` [dpdk-dev] [PATCH v2 3/3] timer: fix rte_timer_reset return value Robert Sanford
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=11399530.HyKjJqreJb@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rsanford2@gmail.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).