<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src, branch stable/9</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=stable%2F9</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=stable%2F9'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2021-05-26T00:27:12Z</updated>
<entry>
<title>arp(8): fixing the deletion failure of IEEE1394 associated addresses</title>
<updated>2021-05-26T00:27:12Z</updated>
<author>
<name>Tai-hwa Liang</name>
<email>avatar@FreeBSD.org</email>
</author>
<published>2021-04-12T06:27:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=59bc2f095289a10b8cfa55cbb2b45c3bd6c2d4ae'/>
<id>urn:sha1:59bc2f095289a10b8cfa55cbb2b45c3bd6c2d4ae</id>
<content type='text'>
Without this, 'arp -d ${IEEE1394_ADDRESS}' gives the following error:

	arp: delete: cannot locate 10.0.0.71

Reviewed by:	glebius
MFC after:	2 weeks

(cherry picked from commit a0d6d0d0b9aba6d4c025b2f2807e7c4b4c4b2415)
</content>
</entry>
<entry>
<title>if_firewire: fixing panic upon packet reception for VNET build</title>
<updated>2021-05-25T23:53:59Z</updated>
<author>
<name>Tai-hwa Liang</name>
<email>avatar@FreeBSD.org</email>
</author>
<published>2021-04-10T15:32:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e0f305d9a99d83a9d4dba7518459a978c67a0059'/>
<id>urn:sha1:e0f305d9a99d83a9d4dba7518459a978c67a0059</id>
<content type='text'>
netisr_dispatch_src() needs valid VNET pointer or firewire_input() will panic
when receiving a packet.

Reviewed by:	glebius
MFC after:	2 weeks

(cherry picked from commit d9b61e7153c64b141436b4d9619b166c6d35a0a6)
</content>
</entry>
<entry>
<title>MFC r363988:</title>
<updated>2020-08-10T17:35:58Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2020-08-10T17:35:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=c60b020b7953b545fcc71b3d27112f31c49b778c'/>
<id>urn:sha1:c60b020b7953b545fcc71b3d27112f31c49b778c</id>
<content type='text'>
Fix clang 11 -Wformat warnings in yp_mkdb:

usr.sbin/yp_mkdb/yp_mkdb.c:91:40: error: format specifies type 'char *' but the argument has type 'void *' [-Werror,-Wformat]
                printf("%.*s %.*s\n", (int)key.size, key.data, (int)data.size,
                        ~~~~                         ^~~~~~~~
usr.sbin/yp_mkdb/yp_mkdb.c:92:7: error: format specifies type 'char *' but the argument has type 'void *' [-Werror,-Wformat]
                    data.data);
                    ^~~~~~~~~
</content>
</entry>
<entry>
<title>MFC r362623:</title>
<updated>2020-06-30T15:53:52Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2020-06-30T15:53:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3d13ece4a9f138915e104c318854b1495d373a9d'/>
<id>urn:sha1:3d13ece4a9f138915e104c318854b1495d373a9d</id>
<content type='text'>
Fix copy/paste mistake in kvm_getswapinfo(3)

It seems this manpage was copied from kvm_getloadavg(3), but the
DIAGNOSTICS section was not updated completely. Update the section with
correct information about a return value of -1.
</content>
</entry>
<entry>
<title>MFC r361977: libusb: improve compatibility</title>
<updated>2020-06-16T12:21:55Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-06-16T12:21:55Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=37b296531c08c1fc8e38ee3e6172dea1ecba5777'/>
<id>urn:sha1:37b296531c08c1fc8e38ee3e6172dea1ecba5777</id>
<content type='text'>
Specifically, add LIBUSB_CLASS_PHYSICAL and the libusb_has_capability API.
Descriptions and functionality for these derived from the
documentation at [0].  The current set of capabilities are all supported by
libusb.

These were detected as missing after updating net/freerdp to 2.1.1, which
attempted to use both.

[0] http://libusb.sourceforge.net/api-1.0/group__libusb__misc.html
</content>
</entry>
<entry>
<title>Adapt merge of r361581 to 9-stable to unbreak kernel compilation.</title>
<updated>2020-06-09T22:15:45Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-09T22:15:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=adbe94a5773e71d863c94185977f43d26f6edde8'/>
<id>urn:sha1:adbe94a5773e71d863c94185977f43d26f6edde8</id>
<content type='text'>
This is a direct commit.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361827:</title>
<updated>2020-06-08T09:35:32Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:35:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5751b9b781602c5be8abd93f1a91c964925f84ad'/>
<id>urn:sha1:5751b9b781602c5be8abd93f1a91c964925f84ad</id>
<content type='text'>
USB HID descriptors may push/pop the current state to allow
description of items residing in a so-called union. FreeBSD currently
only supports 4 such push levels.

If the push level is not restored within the processing of the same
HID item, an invalid memory location may be used for subsequent HID
item processing.

Verify that the push level is always valid when processing HID items.

Reported by:	Andy Nguyen (Google)
Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361582:</title>
<updated>2020-06-08T09:31:52Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:31:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0d65fca72b9842bed6d0a216ae6d37ac69ec6d29'/>
<id>urn:sha1:0d65fca72b9842bed6d0a216ae6d37ac69ec6d29</id>
<content type='text'>
Fix check for wMaxPacketSize in USB bluetooth driver,
in case device is not FULL speed.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361581:</title>
<updated>2020-06-08T09:29:08Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:29:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a8de87d5760d344fb9c63ea8f08ecb68a4d91294'/>
<id>urn:sha1:a8de87d5760d344fb9c63ea8f08ecb68a4d91294</id>
<content type='text'>
Implement helper function, usbd_get_max_frame_length(), which allows kernel
device drivers to correctly predict the default USB transfer frame length.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361577:</title>
<updated>2020-06-08T09:25:40Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:25:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1b1a8a9c00bcf6c3801783fc51ad2e158059841e'/>
<id>urn:sha1:1b1a8a9c00bcf6c3801783fc51ad2e158059841e</id>
<content type='text'>
Don't allow USB device drivers to parent own interface.
It will prevent proper USB device detach.

Sponsored by:	Mellanox Technologies
</content>
</entry>
</feed>
