From: David Miller <davem@davemloft.net>
To: netanel@amazon.com
Cc: netdev@vger.kernel.org, dwmw@amazon.com, zorik@amazon.com,
matua@amazon.com, saeedb@amazon.com, msw@amazon.com,
aliguori@amazon.com, nafea@amazon.com, evgenys@amazon.com,
gtzalik@amazon.com
Subject: Re: [PATCH net V2 0/7] bug fixes for ENA Ethernet driver
Date: Sun, 09 Sep 2018 09:41:08 -0700 (PDT) [thread overview]
Message-ID: <20180909.094108.676476582925729503.davem@davemloft.net> (raw)
In-Reply-To: <20180909081526.83979-1-netanel@amazon.com>
From: <netanel@amazon.com>
Date: Sun, 9 Sep 2018 08:15:19 +0000
> From: Netanel Belgazal <netanel@amazon.com>
>
> Netanel Belgazal (7):
> net: ena: fix surprise unplug NULL dereference kernel crash
> net: ena: fix driver when PAGE_SIZE == 64kB
> net: ena: fix device destruction to gracefully free resources
> net: ena: fix potential double ena_destroy_device()
> net: ena: fix missing lock during device destruction
> net: ena: fix missing calls to READ_ONCE
> net: ena: fix incorrect usage of memory barriers
Series applied, thanks.
prev parent reply other threads:[~2018-09-09 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 8:15 [PATCH net V2 0/7] bug fixes for ENA Ethernet driver netanel
2018-09-09 8:15 ` [PATCH net V2 1/7] net: ena: fix surprise unplug NULL dereference kernel crash netanel
2018-09-09 8:15 ` [PATCH net V2 2/7] net: ena: fix driver when PAGE_SIZE == 64kB netanel
2018-09-09 8:15 ` [PATCH net V2 3/7] net: ena: fix device destruction to gracefully free resources netanel
2018-09-09 8:15 ` [PATCH net V2 4/7] net: ena: fix potential double ena_destroy_device() netanel
2018-09-09 8:15 ` [PATCH net V2 5/7] net: ena: fix missing lock during device destruction netanel
2018-09-09 8:15 ` [PATCH net V2 6/7] net: ena: fix missing calls to READ_ONCE netanel
2018-09-09 8:15 ` [PATCH net V2 7/7] net: ena: fix incorrect usage of memory barriers netanel
2018-09-09 16:41 ` 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=20180909.094108.676476582925729503.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aliguori@amazon.com \
--cc=dwmw@amazon.com \
--cc=evgenys@amazon.com \
--cc=gtzalik@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).