summaryrefslogtreecommitdiff
path: root/bsd/drm_auth.h
diff options
context:
space:
mode:
authorEric Anholt <anholt@freebsd.org>2003-04-26 22:52:39 +0000
committerEric Anholt <anholt@freebsd.org>2003-04-26 22:52:39 +0000
commitce514e08aa8fdbdf52da2ac2cbdace68e0b25210 (patch)
tree4c7101a5f73d5fcface6aeee9b4f599d6a3be9ce /bsd/drm_auth.h
parentf2a0c5438dc83171de1007a68e4f98e35b5a8fbe (diff)
Add PCI DMA memory functions and make addbufs_pci and associated code use
it. To do this we need to save the bus address along with the virtual address in the seglist. Also fix some error handling and a few bits of whitespace.
Diffstat (limited to 'bsd/drm_auth.h')
0 files changed, 0 insertions, 0 deletions
uld result in no warnings or errors and end with a message of the form: ============================================= libdrm-X.Y.Z archives ready for distribution: libdrm-X.Y.Z.tar.gz libdrm-X.Y.Z.tar.bz2 ============================================= Make sure that the version number reported by distcheck and in the tarball names matches the number you bumped to in configure.ac. 6) Commit the configure.ac change and make an annotated tag for that commit with the version number of the release as the name and a message of "libdrm X.Y.Z". For example, for the 2.4.16 release the command is: git tag -a 2.4.16 -m "libdrm 2.4.16" 7) Push the commit and tag by saying git push --tags origin master assuming the remote for the upstream libdrm repo is called origin. 6) Use the release.sh script from the xorg/util/modular repo to upload the tarballs to the freedesktop.org download area and create an annouce email template. The script takes three arguments: a "section", the previous tag and the new tag we just created. For 2.4.16 again, the command is: ../modular/release.sh libdrm 2.4.15 2.4.16 This copies the two tarballs to freedesktop.org and creates libdrm-2.4.16.announce which has a detailed summary of the changes, links to the tarballs, MD5 and SHA1 sums and pre-filled out email headers. Fill out the blank between the email headers and the list of changes with a brief message of what changed or what prompted this release. Send out the email and you're done!