Date: Sat, 30 Apr 2016 02:57:19 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, jenkins-admin@freebsd.org, Kurt Lidl <lidl@pix.net> Subject: Re: Build failed in Jenkins: FreeBSD_HEAD #220 Message-ID: <ab553986-d4ed-520f-f160-a335bb043af6@FreeBSD.org> In-Reply-To: <e4adaa59-f136-f4d4-c045-188847422831@FreeBSD.org> References: <1930955076.5.1461942541071.JavaMail.jenkins@jenkins-9.freebsd.org> <4410839.umQIpSnpkP@ralph.baldwin.cx> <00078caa-226f-77ec-a847-030789483f74@FreeBSD.org> <4214221.s09rEQldUq@ralph.baldwin.cx> <e4adaa59-f136-f4d4-c045-188847422831@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xWRHr4pIA8evNsvk877v6JfL9pgG9EM7V Content-Type: multipart/mixed; boundary="I8jD9uPWC3cekKKRcOgXISOFmBkJMTimm" From: Jung-uk Kim <jkim@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, jenkins-admin@freebsd.org, Kurt Lidl <lidl@pix.net> Message-ID: <ab553986-d4ed-520f-f160-a335bb043af6@FreeBSD.org> Subject: Re: Build failed in Jenkins: FreeBSD_HEAD #220 References: <1930955076.5.1461942541071.JavaMail.jenkins@jenkins-9.freebsd.org> <4410839.umQIpSnpkP@ralph.baldwin.cx> <00078caa-226f-77ec-a847-030789483f74@FreeBSD.org> <4214221.s09rEQldUq@ralph.baldwin.cx> <e4adaa59-f136-f4d4-c045-188847422831@FreeBSD.org> In-Reply-To: <e4adaa59-f136-f4d4-c045-188847422831@FreeBSD.org> --I8jD9uPWC3cekKKRcOgXISOFmBkJMTimm Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 04/29/16 05:46 PM, Jung-uk Kim wrote: > On 04/29/16 05:17 PM, John Baldwin wrote: >> You'll have to talk to the Intel guy who broke this to find out how he= 'd >> like to fix it (not hardcode 32, or fix the AccessWidth). >=20 > I notified Intel guys and they will take care of it. Once they patch > the bug, I'll merge the fix ASAP. It seems it is taking longer than I expected. I reverted the commits from our tree for now (r298838) until we have a proper fix. Sorry for the breakage. Jung-uk Kim --I8jD9uPWC3cekKKRcOgXISOFmBkJMTimm-- --xWRHr4pIA8evNsvk877v6JfL9pgG9EM7V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXJFdWAAoJEHyflib82/FGWacH/i016bQuCZwI5jkN+3XlQAWp knYAb1zmZTUVGL67RETDhgmUBnNgQY/gvobDvgyRN0MNt7a9skPaBJfptrW7Sb6i d6UUx464SIOEurFV03jcUh0pQyZmqseeNOdc+n9qlVbBuLNElPLOnwBFflArV2oR rB5VQ0kXCxH6k0sdVcTXCFPn9fGyS8GfjQGAqNa35axAO7NulS/b5N4OIcmsNIwj jAKcfCvaYmEZVeh0VvPdzIa5+dQpDCf3ZTbGRQ3YuO8AC3iaDCgNlGn/nSkRNHhC G/69JacPd0UqmnNyqfRrRqKNFkXrlQ5ADO2ZmeEr3H7rcwCC0wLiRJCG3uukawI= =MC0v -----END PGP SIGNATURE----- --xWRHr4pIA8evNsvk877v6JfL9pgG9EM7V--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab553986-d4ed-520f-f160-a335bb043af6>