<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/patm, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2017-04-24T21:21:49Z</updated>
<entry>
<title>Remove the NATM framework including the en(4), fatm(4), hatm(4), and</title>
<updated>2017-04-24T21:21:49Z</updated>
<author>
<name>Brooks Davis</name>
<email>brooks@FreeBSD.org</email>
</author>
<published>2017-04-24T21:21:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a7dc31283a053a6c0444813d1432fa83e6ccba9f'/>
<id>urn:sha1:a7dc31283a053a6c0444813d1432fa83e6ccba9f</id>
<content type='text'>
patm(4) devices.

Maintaining an address family and framework has real costs when we make
infrastructure improvements.  In the case of NATM we support no devices
manufactured in the last 20 years and some will not even work in modern
motherboards (some newer devices that patm(4) could be updated to
support apparently exist, but we do not currently have support).

With this change, support remains for some netgraph modules that don't
require NATM support code. It is unclear if all these should remain,
though ng_atmllc certainly stands alone.

Note well: FreeBSD 11 supports NATM and will continue to do so until at
least September 30, 2021.  Improvements to the code in FreeBSD 11 are
certainly welcome.

Reviewed by:	philip
Approved by:	harti
</content>
</entry>
<entry>
<title>sys/dev: Replace zero with NULL for pointers.</title>
<updated>2017-02-20T03:43:12Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-02-20T03:43:12Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4d24901ac9131267fd188c5e1ee19a219847238a'/>
<id>urn:sha1:4d24901ac9131267fd188c5e1ee19a219847238a</id>
<content type='text'>
Makes things easier to read, plus architectures may set NULL to something
different than zero.

Found with:	devel/coccinelle
MFC after:	3 weeks
</content>
</entry>
<entry>
<title>sys/dev: minor spelling fixes.</title>
<updated>2016-05-03T03:41:25Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-05-03T03:41:25Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=453130d9bfc1c6d68b366dfcb041689d69f81295'/>
<id>urn:sha1:453130d9bfc1c6d68b366dfcb041689d69f81295</id>
<content type='text'>
Most affect comments, very few have user-visible effects.
</content>
</entry>
<entry>
<title>sys/dev: extend use of the howmany() macro when available.</title>
<updated>2016-04-26T15:03:15Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-04-26T15:03:15Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=057b4402bf634907fd03590e2757e09e975d04c7'/>
<id>urn:sha1:057b4402bf634907fd03590e2757e09e975d04c7</id>
<content type='text'>
We have a howmany() macro in the &lt;sys/param.h&gt; header that is
convenient to re-use as it makes things easier to read.
</content>
</entry>
<entry>
<title>sys/dev: use our nitems() macro when it is avaliable through param.h.</title>
<updated>2016-04-19T23:37:24Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-04-19T23:37:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=73a1170a8c41cb848f17cc0a8839e9dcee3d126e'/>
<id>urn:sha1:73a1170a8c41cb848f17cc0a8839e9dcee3d126e</id>
<content type='text'>
No functional change, only trivial cases are done in this sweep,
Drivers that can get further enhancements will be done independently.

Discussed in:	freebsd-current
</content>
</entry>
<entry>
<title>Cleanup unnecessary semicolons from the kernel.</title>
<updated>2016-04-10T23:07:00Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-04-10T23:07:00Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=74b8d63dcc17c07d8cb21e13f6db517698efd49f'/>
<id>urn:sha1:74b8d63dcc17c07d8cb21e13f6db517698efd49f</id>
<content type='text'>
Found with devel/coccinelle.
</content>
</entry>
<entry>
<title>Fix LDADD/DPADD that should be LIBADD.</title>
<updated>2015-12-04T03:17:47Z</updated>
<author>
<name>Bryan Drewery</name>
<email>bdrewery@FreeBSD.org</email>
</author>
<published>2015-12-04T03:17:47Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=eacae6dc66aa881c102f11e2003174eea7e8af74'/>
<id>urn:sha1:eacae6dc66aa881c102f11e2003174eea7e8af74</id>
<content type='text'>
Sponsored by:	EMC / Isilon Storage Division
</content>
</entry>
<entry>
<title>CALLOUT_MPSAFE has lost its meaning since r141428, i.e., for more than ten</title>
<updated>2015-05-22T17:05:21Z</updated>
<author>
<name>Jung-uk Kim</name>
<email>jkim@FreeBSD.org</email>
</author>
<published>2015-05-22T17:05:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=fd90e2ed54a69bb07d14dcd4e805431ccb7d6cb6'/>
<id>urn:sha1:fd90e2ed54a69bb07d14dcd4e805431ccb7d6cb6</id>
<content type='text'>
years for head.  However, it is continuously misused as the mpsafe argument
for callout_init(9).  Deprecate the flag and clean up callout_init() calls
to make them more consistent.

Differential Revision:	https://reviews.freebsd.org/D2613
Reviewed by:	jhb
MFC after:	2 weeks
</content>
</entry>
<entry>
<title>To ease changes to underlying mbuf structure and the mbuf allocator, reduce</title>
<updated>2015-01-05T09:58:32Z</updated>
<author>
<name>Robert Watson</name>
<email>rwatson@FreeBSD.org</email>
</author>
<published>2015-01-05T09:58:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ed6a66ca6c2065bc1fed93e00805676a5d3b981e'/>
<id>urn:sha1:ed6a66ca6c2065bc1fed93e00805676a5d3b981e</id>
<content type='text'>
the knowledge of mbuf layout, and in particular constants such as M_EXT,
MLEN, MHLEN, and so on, in mbuf consumers by unifying various alignment
utility functions (M_ALIGN(), MH_ALIGN(), MEXT_ALIGN() in a single
M_ALIGN() macro, implemented by a now-inlined m_align() function:

- Move m_align() from uipc_mbuf.c to mbuf.h; mark as __inline.
- Reimplement M_ALIGN(), MH_ALIGN(), and MEXT_ALIGN() using m_align().
- Update consumers around the tree to simply use M_ALIGN().

This change eliminates a number of cases where mbuf consumers must be aware
of whether or not mbufs returned by the allocator use external storage, but
also assumptions about the size of the returned mbuf. This will make it
easier to introduce changes in how we use external storage, as well as
features such as variable-size mbufs.

Differential Revision:	https://reviews.freebsd.org/D1436
Reviewed by:	glebius, trasz, gnn, bz
Sponsored by:	EMC / Isilon Storage Division
</content>
</entry>
<entry>
<title>Follow up to r225617. In order to maximize the re-usability of kernel code</title>
<updated>2014-10-16T18:04:43Z</updated>
<author>
<name>Davide Italiano</name>
<email>davide@FreeBSD.org</email>
</author>
<published>2014-10-16T18:04:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2be111bf7dda0f18d645f0e201b6555bbe3da1ac'/>
<id>urn:sha1:2be111bf7dda0f18d645f0e201b6555bbe3da1ac</id>
<content type='text'>
in userland rename in-kernel getenv()/setenv() to kern_setenv()/kern_getenv().
This fixes a namespace collision with libc symbols.

Submitted by:   kmacy
Tested by:      make universe
</content>
</entry>
</feed>
