From: Leon Romanovsky <leon@kernel.org>
To: Gal Pressman <galpress@amazon.com>
Cc: "Håkon Bugge" <haakon.bugge@oracle.com>,
"Jason Gunthorpe" <jgg@mellanox.com>,
"OFED mailing list" <linux-rdma@vger.kernel.org>,
"Yishai Hadas" <yishaih@mellanox.com>,
"Jack Morgenstein" <jackm@dev.mellanox.co.il>,
ranro@mellanox.com
Subject: Re: [PATCH for-rc v2 0/6] Add CM packets missing and harden the proxying
Date: Mon, 10 Aug 2020 17:23:36 +0300 [thread overview]
Message-ID: <20200810142336.GB20478@unreal> (raw)
In-Reply-To: <b31db3dc-437c-a61f-815c-418cf436861f@amazon.com>
On Mon, Aug 10, 2020 at 05:10:44PM +0300, Gal Pressman wrote:
> On 10/08/2020 14:46, Leon Romanovsky wrote:
> > On Mon, Aug 10, 2020 at 01:20:43PM +0200, Håkon Bugge wrote:
> >> A friendly reminder.
> >
> > We are in merge window.
>
> The merge window shouldn't affect bug fixes submissions, no?
It is hard to call bug fixes, according to Fixes line and description
the code is broken from day one. There is no urgency to merge it now.
Thanks
next prev parent reply other threads:[~2020-08-10 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:19 [PATCH for-rc v2 0/6] Add CM packets missing and harden the proxying Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 1/6] IB/mlx4: Add and improve logging Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 2/6] IB/mlx4: Add support for MRA Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 3/6] IB/mlx4: Separate tunnel and wire bufs parameters Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 4/6] IB/mlx4: Fix starvation in paravirt mux/demux Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 5/6] IB/mlx4: Add support for REJ due to timeout Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 6/6] IB/mlx4: Adjust delayed work when a dup is observed Håkon Bugge
2020-08-10 11:20 ` [PATCH for-rc v2 0/6] Add CM packets missing and harden the proxying Håkon Bugge
2020-08-10 11:46 ` Leon Romanovsky
2020-08-10 14:10 ` Gal Pressman
2020-08-10 14:23 ` Leon Romanovsky [this message]
2020-08-24 16:36 ` Jason Gunthorpe
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=20200810142336.GB20478@unreal \
--to=leon@kernel.org \
--cc=galpress@amazon.com \
--cc=haakon.bugge@oracle.com \
--cc=jackm@dev.mellanox.co.il \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=ranro@mellanox.com \
--cc=yishaih@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