From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] bnxt_en: Updates for net-next.
Date: Thu, 31 Oct 2019 14:48:51 -0700 (PDT) [thread overview]
Message-ID: <20191031.144851.211645703557989376.davem@davemloft.net> (raw)
In-Reply-To: <1572498471-31550-1-git-send-email-michael.chan@broadcom.com>
From: Michael Chan <michael.chan@broadcom.com>
Date: Thu, 31 Oct 2019 01:07:44 -0400
> This patch series adds TC Flower tunnel decap and rewrite actions in
> the first 4 patches. The next 3 patches integrates the recently
> added error recovery with the RDMA driver by calling the proper
> hooks to stop and start.
>
> v2: Fix pointer alignment issue in patch #1.
Series applied, thanks Michael.
prev parent reply other threads:[~2019-10-31 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 5:07 [PATCH net-next v2 0/7] bnxt_en: Updates for net-next Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 1/7] bnxt_en: Add support for L2 rewrite Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 2/7] bnxt: Avoid logging an unnecessary message when a flow can't be offloaded Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 3/7] bnxt_en: Add support for NAT(L3/L4 rewrite) Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 4/7] bnxt_en: flow_offload: offload tunnel decap rules via indirect callbacks Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 5/7] bnxt_en: Improve bnxt_ulp_stop()/bnxt_ulp_start() call sequence Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 6/7] bnxt_en: Call bnxt_ulp_stop()/bnxt_ulp_start() during error recovery Michael Chan
2019-10-31 5:07 ` [PATCH net-next v2 7/7] bnxt_en: Call bnxt_ulp_stop()/bnxt_ulp_start() during suspend/resume Michael Chan
2019-10-31 21:48 ` 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=20191031.144851.211645703557989376.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.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).