Page MenuHomeFreeBSD

sound: Fix SEQ_SYSEX() macro
AbandonedPublic

Authored by christos on Aug 20 2024, 11:32 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 28 2025, 6:26 AM
Unknown Object (File)
Dec 28 2025, 2:06 AM
Unknown Object (File)
Dec 1 2025, 4:09 PM
Unknown Object (File)
Nov 18 2025, 4:24 AM
Unknown Object (File)
Nov 3 2025, 10:28 PM
Unknown Object (File)
Nov 3 2025, 10:28 PM
Unknown Object (File)
Nov 3 2025, 6:45 PM
Unknown Object (File)
Oct 30 2025, 10:08 AM
Subscribers

Details

Reviewers
markj
emaste
Summary

Correct implementation also found in Linux's soundcard.h:
https://github.com/torvalds/linux/blob/master/include/uapi/linux/soundcard.h#L1178

seq_processevent() interprets event[1] as device number and does not
work properly with current SEQ_SYSEX() implementation.

MFC after: 2 days
Sponsored by: The FreeBSD Foundation
Pull Request: https://github.com/freebsd/freebsd-src/pull/1374

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 59105
Build 55992: arc lint + arc unit

Event Timeline

Bump.

Isn't this the same as the patch submitted by Ivan on github? https://github.com/freebsd/freebsd-src/pull/1374

If so, and you think the patch is reasonable, you can just approve it and we'll take care of landing it into src with the correct attribution etc..

Bump.

Isn't this the same as the patch submitted by Ivan on github? https://github.com/freebsd/freebsd-src/pull/1374

If so, and you think the patch is reasonable, you can just approve it and we'll take care of landing it into src with the correct attribution etc..

It is (see "Pull request").

Bump.

Isn't this the same as the patch submitted by Ivan on github? https://github.com/freebsd/freebsd-src/pull/1374

If so, and you think the patch is reasonable, you can just approve it and we'll take care of landing it into src with the correct attribution etc..

It is (see "Pull request").

Then there's no need to create a phabricator review. It sounds like the commit message should be improved; you can make a suggestion there and ask the submitter to re-push their patch with a better commit log message. If you're happy with the patch, just click "approve".

Alright, didn't know we could use just GitHub for this. Thank you. :)