| /freebsd/sys/dev/iicbus/mux/ |
| H A D | pca9547.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| H A D | iic_gpiomux.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| H A D | ltc430x.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| /freebsd/sys/dev/gpio/ |
| H A D | gpiopps.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| H A D | gpioths.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| H A D | gpioiic.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| /freebsd/sys/arm/ti/am335x/ |
| H A D | am335x_ehrpwm.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| H A D | am335x_dmtpps.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| /freebsd/sys/dev/pwm/ |
| H A D | pwmc.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|
| /freebsd/sys/dev/ow/ |
| H A D | owc_gpiobus.c | diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
diff 519b64e2 Sat Jan 23 15:55:09 GMT 2021 Mark Johnston <markj@FreeBSD.org> Revert "Define PNP info after defining driver modules"
This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae.
The reverted commit was motivated by a problem observed on stable/12,
but it turns out that a better solution was committed in r348309 but not
MFCed. So, revert this change since it is unnecessary and not really
correct: it assumes that the order in which module metadata records is
defined determines their order in the output linker set. While this
seems to hold in my testing, it is not guaranteed.
Reported by: cem
Discussed with: imp
MFC after: 3 days
|