| 20991c24 | 25-Oct-2018 |
Hans Petter Selasky <[email protected]> |
MFC r339582: Drop sequencer mutex around uiomove() and make sure we don't move more bytes than is available, else a panic might happen.
Found by: Peter Holm <[email protected]> Approved by: re (rgrime
MFC r339582: Drop sequencer mutex around uiomove() and make sure we don't move more bytes than is available, else a panic might happen.
Found by: Peter Holm <[email protected]> Approved by: re (rgrimes) Sponsored by: Mellanox Technologies
show more ...
|
| bf466ddc | 01-Sep-2018 |
Glen Barber <[email protected]> |
Revert r338423, reapplying r338422, which did get approval but communication lines got crossed.
Apologies to avatar@ for the confusion.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundati
Revert r338423, reapplying r338422, which did get approval but communication lines got crossed.
Apologies to avatar@ for the confusion.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
show more ...
|
| 076cf2dd | 18-Aug-2015 |
Tai-hwa Liang <[email protected]> |
Using the error return code documented in the comment.
Though there is no direct midi_uninit() caller amongst existing drivers at this moment, a quick experiment indicates that EBUSY gives users mor
Using the error return code documented in the comment.
Though there is no direct midi_uninit() caller amongst existing drivers at this moment, a quick experiment indicates that EBUSY gives users more precise error message once drivers start to honour this result. For example, emu_midi_detach() should check the result of mpu401_uninit() and block module unloading if there is any MIDI I/O in progress.
MFC after: 2 weeks
show more ...
|