From: David Miller <davem@davemloft.net>
To: michal.kalderon@marvell.com
Cc: ariel.elior@marvell.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net 0/2] qed: iWARP - fix some syn related issues.
Date: Mon, 18 Feb 2019 16:52:12 -0800 (PST) [thread overview]
Message-ID: <20190218.165212.152079603884022949.davem@davemloft.net> (raw)
In-Reply-To: <20190218132403.12487-1-michal.kalderon@marvell.com>
From: Michal Kalderon <michal.kalderon@marvell.com>
Date: Mon, 18 Feb 2019 15:24:01 +0200
> This series fixes two bugs related to iWARP syn processing flow.
Series applied, thanks.
prev parent reply other threads:[~2019-02-19 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 13:24 [PATCH net 0/2] qed: iWARP - fix some syn related issues Michal Kalderon
2019-02-18 13:24 ` [PATCH net 1/2] qed: Fix iWARP buffer size provided for syn packet processing Michal Kalderon
2019-02-18 13:24 ` [PATCH net 2/2] qed: Fix iWARP syn packet mac address validation Michal Kalderon
2019-02-19 0:52 ` 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=20190218.165212.152079603884022949.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariel.elior@marvell.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michal.kalderon@marvell.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