I don't think this is the right time to rush and commit big diffs which noone can actively test, not even build on all architectures, because there are no snapshots being built, because the tree is semi-frozen to make a release. visa is right.
Visa Hankala <v...@hankala.org> wrote: > On Mon, Apr 11, 2022 at 07:14:46PM +0200, Martin Pieuchot wrote: > > Now that poll(2) & select(2) use the kqueue backend under the hood we > > can start retiring the old machinery. > > > > The diff below does not touch driver definitions, however it : > > > > - kills selrecord() & doselwakeup() > > > > - make it obvious that `kern.nselcoll' is now always 0 > > > > - Change all poll/select hooks to return 0 > > > > - Kill a seltid check in wsdisplaystart() which is now always true > > > > In a later step we could remove the *_poll() requirement from device > > drivers and kill seltrue() & selfalse(). > > > > ok? > > I was planning to wait for two weeks after the general availability > of the 7.1 release, and then begin the dismantling in logical order > from fo_poll. > > The final tier of the new code's testing will begin when release users > upgrade their production machines. Because of this, I would refrain > from burning bridges just yet. >
