From: "Agarwal, Anchal" <anchalag@amazon.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
Anchal Agarwal <anchalag@amzn.com>,
"Oleksandr_Andrushchenko@epam.com"
<Oleksandr_Andrushchenko@epam.com>
Cc: "Kamata, Munehisa" <kamatam@amazon.com>,
Julien Grall <julien.grall@arm.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jgross@suse.com" <jgross@suse.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Artem Mygaiev <Artem_Mygaiev@epam.com>
Subject: Re: [Xen-devel] [PATCH] xen/netfront: Remove unneeded .resume callback
Date: Thu, 30 May 2019 12:32:19 +0000 [thread overview]
Message-ID: <F76E91F5-0981-4233-A7F9-072B7026D404@amazon.com> (raw)
In-Reply-To: <48fedb13-5af2-e7cf-d182-0f2bb385dda2@gmail.com>
Hi Oleksandr,
Hello, Anchal!
On 3/29/19 1:19 AM, Anchal Agarwal wrote:
[snip]
>>>> Great, could you please let us know what is the progress and further plans
>>>> on that, so we do not work on the same code and can coordinate our
>>>> efforts somehow? Anchal, could you please shed some light on this?
>>> Looks like my previous email did not make it to mailing list. May be some issues with my
>>> email server settings. Giving it another shot.
>>> Yes, I am working on those patches and plan to re-post them in an effort to upstream.
>> This is really great, looking forward to it: any date in your mind
>> when this can happen?
> Not a specific date but may be in few weeks. I am currently swamped at work.
>
Any progress on this?
Yes, but at a snail's pace.
Thank you,
Oleksandr
Thanks,
Anchal
prev parent reply other threads:[~2019-05-30 12:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 13:17 [Xen-devel][PATCH] xen/netfront: Remove unneeded .resume callback Oleksandr Andrushchenko
2019-03-14 13:50 ` Oleksandr Andrushchenko
2019-03-14 14:47 ` Boris Ostrovsky
2019-03-14 14:52 ` Oleksandr Andrushchenko
2019-03-14 15:02 ` Boris Ostrovsky
2019-03-14 15:10 ` Oleksandr Andrushchenko
2019-03-14 15:40 ` Boris Ostrovsky
2019-03-14 16:33 ` Oleksandr Andrushchenko
2019-03-14 18:16 ` Boris Ostrovsky
2019-03-14 18:20 ` Oleksandr Andrushchenko
2019-03-14 19:00 ` [Xen-devel] [PATCH] " Julien Grall
2019-03-18 10:02 ` Oleksandr Andrushchenko
2019-03-20 3:50 ` Munehisa Kamata
2019-03-22 10:44 ` Oleksandr Andrushchenko
[not found] ` <20190325173011.GA20277@kaos-source-ops-60001.pdx1.amazon.com>
2019-03-27 6:40 ` Oleksandr Andrushchenko
[not found] ` <20190328231928.GA5172@kaos-source-ops-60001.pdx1.amazon.com>
2019-05-16 6:26 ` Oleksandr Andrushchenko
2019-05-30 12:32 ` Agarwal, Anchal [this message]
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=F76E91F5-0981-4233-A7F9-072B7026D404@amazon.com \
--to=anchalag@amazon.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Oleksandr_Andrushchenko@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=anchalag@amzn.com \
--cc=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=kamatam@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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).