From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org, ogerlitz@mellanox.com,
talal@mellanox.com, eranbe@mellanox.com
Subject: Re: [PATCH net 0/4] Mellanox 100G mlx5 fixes for 4.6-rc
Date: Tue, 03 May 2016 13:37:47 -0400 (EDT) [thread overview]
Message-ID: <20160503.133747.1459772515243143845.davem@davemloft.net> (raw)
In-Reply-To: <1462132797-22853-1-git-send-email-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Sun, 1 May 2016 22:59:53 +0300
> This small series provides some bug fixes for mlx5 driver.
>
> A small bug fix for iounmap of a null pointer, which dumps a warning on some archs.
>
> One patch to fix the VXLAN/MLX5_EN dependency issue reported by Arnd.
>
> Two patches to fix the scheduling while atomic issue for ndo_add/del_vxlan_port
> NDOs. The first will add an internal mlx5e workqueue and the second will
> delegate vxlan ports add/del requests to that workqueue.
>
> Note: ('net/mlx5: Kconfig: Fix MLX5_EN/VXLAN build issue') is only needed for net
> and not net-next as the issue was globally fixed for all device drivers by:
> b7aade15485a ('vxlan: break dependency with netdev drivers') in net-next.
>
> Applied on top: f27337e16f2d ('ip_tunnel: fix preempt warning in ip tunnel creation/updating')
Series applied, thanks.
prev parent reply other threads:[~2016-05-03 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 19:59 [PATCH net 0/4] Mellanox 100G mlx5 fixes for 4.6-rc Saeed Mahameed
2016-05-01 19:59 ` [PATCH net 1/4] net/mlx5: Unmap only the relevant IO memory mapping Saeed Mahameed
2016-05-01 19:59 ` [PATCH net 2/4] net/mlx5: Kconfig: Fix MLX5_EN/VXLAN build issue Saeed Mahameed
2016-05-01 19:59 ` [PATCH net 3/4] net/mlx5e: Implement a mlx5e workqueue Saeed Mahameed
2016-05-01 19:59 ` [PATCH net 4/4] net/mlx5e: Use workqueue for vxlan ops Saeed Mahameed
2016-05-03 17:37 ` 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=20160503.133747.1459772515243143845.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eranbe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=talal@mellanox.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).