From: David Miller <davem@davemloft.net>
To: netanel@amazon.com
Cc: netdev@vger.kernel.org, dwmw@amazon.co.uk, zorik@amazon.com,
matua@amazon.com, saeedb@amazon.com, msw@amazon.com,
aliguori@amazon.com, nafea@amazon.com, evgenys@amazon.com
Subject: Re: [PATCH net 0/9] Bugs fixes in ena ethernet driver
Date: Mon, 12 Jun 2017 10:24:32 -0400 (EDT) [thread overview]
Message-ID: <20170612.102432.2053652648532805091.davem@davemloft.net> (raw)
In-Reply-To: <1497276570720.79426@amazon.com>
From: "Belgazal, Netanel" <netanel@amazon.com>
Date: Mon, 12 Jun 2017 14:09:30 +0000
> Do you might have an ETA when do you plan to merge net branch into
> net-next? I plan to base my new patchset to net-next on top of this
> one.
Probably later in the week, either Tuesday or Weds.
prev parent reply other threads:[~2017-06-12 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 12:42 [PATCH net 0/9] Bugs fixes in ena ethernet driver netanel
2017-06-11 12:42 ` [PATCH net 1/9] net: ena: fix rare uncompleted admin command false alarm netanel
2017-06-11 12:42 ` [PATCH net 2/9] net: ena: fix bug that might cause hang after consecutive open/close interface netanel
2017-06-11 12:42 ` [PATCH net 3/9] net: ena: add missing return when ena_com_get_io_handlers() fails netanel
2017-06-11 12:42 ` [PATCH net 4/9] net: ena: fix race condition between submit and completion admin command netanel
2017-06-11 12:42 ` [PATCH net 5/9] net: ena: add missing unmap bars on device removal netanel
2017-06-11 12:42 ` [PATCH net 6/9] net: ena: fix theoretical Rx hang on low memory systems netanel
2017-06-11 12:42 ` [PATCH net 7/9] net: ena: disable admin msix while working in polling mode netanel
2017-06-11 12:42 ` [PATCH net 8/9] net: ena: bug fix in lost tx packets detection mechanism netanel
2017-06-11 12:42 ` [PATCH net 9/9] net: ena: update ena driver to version 1.1.7 netanel
2017-06-11 20:38 ` [PATCH net 0/9] Bugs fixes in ena ethernet driver David Miller
2017-06-12 14:09 ` Belgazal, Netanel
2017-06-12 14:24 ` David Miller [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=20170612.102432.2053652648532805091.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aliguori@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=evgenys@amazon.com \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=zorik@amazon.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).