From: David Miller <davem@davemloft.net>
To: galp@mellanox.com
Cc: netdev@vger.kernel.org, tariqt@mellanox.com, saeedm@mellanox.com
Subject: Re: [PATCH net-next v2 0/6] Replace WARN_ONCE usages with netdev_WARN_ONCE
Date: Mon, 08 Jan 2018 20:53:30 -0500 (EST) [thread overview]
Message-ID: <20180108.205330.906857600778390511.davem@davemloft.net> (raw)
In-Reply-To: <1515319720-18428-1-git-send-email-galp@mellanox.com>
From: Gal Pressman <galp@mellanox.com>
Date: Sun, 7 Jan 2018 12:08:34 +0200
> This series will fix an issue in netdev_WARN_ONCE, improve its formatting and
> replace drivers' usage of WARN_ONCE to netdev_WARN_ONCE.
>
> Driver specific patches were compilation tested, in addition, functional tested
> on Mellanox NIC.
>
> v1->v2:
> - Addressed commit message comments in patch #1
Series applied, thanks.
prev parent reply other threads:[~2018-01-09 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 10:08 [PATCH net-next v2 0/6] Replace WARN_ONCE usages with netdev_WARN_ONCE Gal Pressman
2018-01-07 10:08 ` [PATCH net-next v2 1/6] net: Fix netdev_WARN_ONCE macro Gal Pressman
2018-01-09 2:42 ` Joe Perches
2018-01-09 3:05 ` David Miller
2018-01-09 9:51 ` Gal Pressman
2018-01-07 10:08 ` [PATCH net-next v2 2/6] net: No line break on netdev_WARN* formatting Gal Pressman
2018-01-07 10:08 ` [PATCH net-next v2 3/6] net/mlx5e: Replace WARN_ONCE with netdev_WARN_ONCE Gal Pressman
2018-01-07 10:08 ` [PATCH net-next v2 4/6] e1000: " Gal Pressman
2018-01-07 10:08 ` [PATCH net-next v2 5/6] bnx2x: " Gal Pressman
2018-01-09 2:40 ` Kalluru, Sudarsana
2018-01-07 10:08 ` [PATCH net-next v2 6/6] 8139cp: " Gal Pressman
2018-01-09 1:53 ` 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=20180108.205330.906857600778390511.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=galp@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@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).