Am 13.11.2018 um 19:45 schrieb Scott Long:


On Nov 13, 2018, at 11:11 AM, Harry Schmalzbauer <free...@omnilan.de> wrote:

Am 13.11.2018 um 19:02 schrieb Scott Long:
On Nov 12, 2018, at 10:03 AM, Harry Schmalzbauer <free...@omnilan.de> wrote:

Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer:
Am 05.06.2018 um 19:54 schrieb Scott Long:
…
Late in the 11.2 phase, I identified this commit as a regression for MSI 
(non-x) alloctaion.

thanks a lot, in fact I'm not surprised that you come up with a better solution 
than that quick fix :-)
Had hoped someone else would do an intermediate commit to get it into 12.0 in 
time, so you won't feel any time pressure - good job needs the time it needs, 
as long as the right person is doing the job.

Unfortunately I don't have a non-productive setup where I could test before 
release/12.0 will be branched – might be subject to change...

12.0 has completely different code from 11.x, and from my review of it last 
night it should be fine.  If you have evidence that what’s currently in 12 is 
not working, please let me know ASAP.

Sorry for the confusion, I missed that.
I just verified that I do apply the patch (without errors) to local stable/12 source tree for local releases... That's probably a mistake. I can't remember if I ever checked whether stable/12 (for sure not stable/12, but -current back then) MSI fallback allocation does work without the patch or not.

Like metioned, I don't have a non-productive machine of that kind for testing, but it's superfluous anyways if you know that code paths differ in that part.

Please ignore my 12.0 referings, sorry.

-harry

_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to