Skip to content

sys/unix: add Mmsghdr for linux - #284

Open
nickgarlis wants to merge 1 commit into
golang:masterfrom
nickgarlis:add-mmsghdr
Open

sys/unix: add Mmsghdr for linux#284
nickgarlis wants to merge 1 commit into
golang:masterfrom
nickgarlis:add-mmsghdr

Conversation

@nickgarlis

Copy link
Copy Markdown
Contributor

Expose struct mmsghdr as Mmsghdr, along with SizeofMmsghdr, so
callers can build recvmmsg(2) without redefining the types per
architecture.

This is split out from the Recvmmsg wrapper proposed in
golang/go#80434, since that API is still under discussion and this
change itself is non-controversial.

Updates golang/go#80434

Expose struct mmsghdr as Mmsghdr, along with SizeofMmsghdr, so
callers can build recvmmsg(2) without redifining the types per
architecture.

This is split out from the Recvmmsg wrapper proposed in
golang/go#80434, since that API is still under discussion and this
change itself is non-controversial.

Updates golang/go#80434
@gopherbot

Copy link
Copy Markdown
Contributor

This PR (HEAD: f0c5daa) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/812300.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants