Re: armel after Stretch

To: debian-arm@lists.debian.org
Cc: debian-devel@lists.debian.org
Subject: Re: armel after Stretch
From: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Wed, 14 Dec 2016 09:28:39 -0500
Message-id: <[🔎] jwveg1aoaaj.fsf-monnier+gmane.linux.debian.ports.arm@gnu.org>
References: <20160722013605.GA854@einval.com> <[🔎] 20161207205040.07d1008522b3ce892cba9a50@gmail.com> <[🔎] 20161207155331.GC12572@einval.com> <[🔎] 20161213235206.wgsmpmyeokllsyzf@roeckx.be>

> I was under the impression that that's not the case:
> https://lwn.net/Articles/314561/

Aha!  Using the same trick that was used in the Mach microkernel.


        Stefan

Reply to:

References:
- armel after Stretch (was: Summary of the ARM ports BoF at DC16)
  - From: Roger Shimizu <rogershimizu@gmail.com>
- Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)
  - From: Steve McIntyre <steve@einval.com>
- Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)
  - From: Kurt Roeckx <kurt@roeckx.be>

Prev by Date: Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)
Next by Date: Rslsync (former BTSync) on Kirkwood, Hash faults
Previous by thread: Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)
Next by thread: Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)
Index(es):
- Date
- Thread