From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: linux-next: manual merge of the mlx5-next tree with the rdma tree Date: Wed, 5 Dec 2018 13:10:50 +1100 Message-ID: <20181205131050.40ab2924@canb.auug.org.au> References: <20181205120706.294b9422@canb.auug.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/vG645c4b6W9KXzOY2s6rz7x"; protocol="application/pgp-signature" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Doug Ledford Cc: Leon Romanovsky , Jason Gunthorpe , Linux Next Mailing List , Linux Kernel Mailing List List-Id: linux-next.vger.kernel.org --Sig_/vG645c4b6W9KXzOY2s6rz7x Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Doug, On Tue, 04 Dec 2018 20:33:08 -0500 Doug Ledford wrote: > > FWIW this will go away in a day or two. I merged mlx5-next into rdma > for-next in order to take a series that depended on it. Understood, thanks. --=20 Cheers, Stephen Rothwell --Sig_/vG645c4b6W9KXzOY2s6rz7x Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlwHM6oACgkQAVBC80lX 0GzOJwf/SCt5nIq9akTUi/0Js6T48he9Lzl2FF6YTU4b9Z6l4Nhv6NCIjS5siEOS j7HifJEBkW+zwzIXVjGq1U9ZMrBy8ZJQSux16x60B4Er5RuYp4VmsbDGdmmP8D8A ESmtQdoQEKnr3I4G3qkEhveJPBSc2DKlkLXCOxH2f9SJc6A5xY9z6KboUT7ebJ9W 9t+gbv49UxkU+mVh4muRVnYbA8KK3/iBHc0NnZxaUQZpl/chgAe2YEYyaOd2XmOi /VWtPeuJOSVrSMJuBMovA7BQHAkjR6sQUK6DCqKVTO+qhG94n1kSkyzSxo+S0LMp jwgm3hCToxPRhv7vBWdHdd/DOmlSlg== =6VdL -----END PGP SIGNATURE----- --Sig_/vG645c4b6W9KXzOY2s6rz7x--