From: Thomas Monjalon <thomas@monjalon.net>
To: Harman Kalra <hkalra@marvell.com>
Cc: stephen@networkplumber.org, jgrajcia@cisco.com,
david.marchand@redhat.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] eal: fix epoll fd list rebuild
Date: Wed, 27 May 2020 15:04:04 +0200 [thread overview]
Message-ID: <1609476.kT2rm9d7Co@thomas> (raw)
In-Reply-To: <20200527124425.GA23064@outlook.office365.com>
27/05/2020 14:44, Harman Kalra:
> On Wed, May 27, 2020 at 06:02:53PM +0530, Harman Kalra wrote:
> > On Mon, May 25, 2020 at 03:19:08PM +0530, Harman Kalra wrote:
> > > On Sun, May 24, 2020 at 05:30:26PM +0200, Thomas Monjalon wrote:
> > > > This patch is missing 20.05 because no review was done.
> > > > In general, we are missing a maintainer on "interrupts" area.
> >
> > Ping.
> >
> > > Hi Thomas,
> > >
> > > If everybody is fine we can take up the responsibility of maintaining
> > > interrupt subsystem. I can send a patch to update maintainer list for
> > > the same.
>
> Sorry for wrong placement of ping in my last mail, as it is bit
> confusing if it was for the patch.
>
> Rather intention of this ping is to get input if we can take up the
> maintainership of interrupt subsystem to help the community with the
> reviews.
Please Cc everybody who contributed to this code.
Thanks
next prev parent reply other threads:[~2020-05-27 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:43 [dpdk-dev] [PATCH] eal: fix epoll fd list rebuild Harman Kalra
2020-05-24 15:30 ` Thomas Monjalon
2020-05-25 9:49 ` [dpdk-dev] [EXT] " Harman Kalra
2020-05-27 12:32 ` Harman Kalra
2020-05-27 12:44 ` Harman Kalra
2020-05-27 13:04 ` Thomas Monjalon [this message]
2020-05-27 17:19 ` Harman Kalra
2020-06-19 13:59 ` [dpdk-dev] [PATCH v2] " Harman Kalra
2020-06-24 8:01 ` Thomas Monjalon
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=1609476.kT2rm9d7Co@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jgrajcia@cisco.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.