From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: manual merge of the mfd tree with the
 drm-intel tree
Date: Tue, 21 Aug 2018 18:33:12 +1000
Message-ID: <20180821183312.690df265@canb.auug.org.au>
References: <20180726151006.345e8397@canb.auug.org.au>
 <20180816121256.0435930e@canb.auug.org.au>
 <CAMuHMdXtMer6z09GV4HM++0RjYSkLWaXO9-m==SE85RkQ2xP-g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0469418141=="
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
In-Reply-To: <CAMuHMdXtMer6z09GV4HM++0RjYSkLWaXO9-m==SE85RkQ2xP-g@mail.gmail.com>
List-Unsubscribe: <https://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <https://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <https://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: paulo.r.zanoni@intel.com, Neil Armstrong <narmstrong@baylibre.com>, Daniel Vetter <daniel.vetter@ffwll.ch>, Intel Graphics Development <intel-gfx@lists.freedesktop.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux-Next <linux-next@vger.kernel.org>, DRI Development <dri-devel@lists.freedesktop.org>, rodrigo.vivi@intel.com, Lee Jones <lee.jones@linaro.org>
List-Id: dri-devel@lists.freedesktop.org

--===============0469418141==
Content-Type: multipart/signed; micalg=pgp-sha256;
 boundary="Sig_/mN/pLNHOeUnbSuu_2uXBwAG"; protocol="application/pgp-signature"

--Sig_/mN/pLNHOeUnbSuu_2uXBwAG
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Geert,

On Tue, 21 Aug 2018 10:27:48 +0200 Geert Uytterhoeven <geert@linux-m68k.org=
> wrote:
>=20
> FTR, it's not this one, but the similar one reported on Jul 19, which doe=
s not
> add the tc_port_type enum.

Right, sorry about that.  Linus has now merged the mfd tree so things
are probably done now.

--=20
Cheers,
Stephen Rothwell

--Sig_/mN/pLNHOeUnbSuu_2uXBwAG
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlt7zkgACgkQAVBC80lX
0GwumggAmMYtZ3+bsBuQAv5rMt7IvUeVl7q1oyOShdcVYns81DVI+DPRGTqedocx
e3A8bkMNXOpD6Lj4aOCoxWSxBuLnxBw+bWZyUTmYvnpi6HqU+htsNWaikvTpU8TL
wSzdJ3X3n5AJKv/C+ndtLT/Ie0F9vIfELBuYzE1DKs0YvFAhqZsXahkJbN5di0NN
RUy52qBjTJj1UIjMs0gaCo+/WFI7Eb6cr/GOjufPi2x+9zgbl29jOsU96c4pbxyM
tA/UcsCWd2ns1dKT6BnRM4SpbvdUcEGnalE1HSc7KszpLyIgcNAO0KXsYwd3yQds
Ao6gDzSgovN3B+bky87Ah9ynfy+J+g==
=pvwd
-----END PGP SIGNATURE-----

--Sig_/mN/pLNHOeUnbSuu_2uXBwAG--

--===============0469418141==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSW50ZWwtZ2Z4
IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vaW50ZWwtZ2Z4Cg==

--===============0469418141==--