<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/Documentation/networking/representors.rst, branch linux-rolling-lts</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-lts</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-lts'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2024-03-29T01:20:08Z</updated>
<entry>
<title>Documentation: Add documentation for eswitch attribute</title>
<updated>2024-03-29T01:20:08Z</updated>
<author>
<name>William Tu</name>
</author>
<published>2024-03-25T18:12:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=931ec1e4cb7fd81fe01e85419238a9cfb9d930c9'/>
<id>urn:sha1:931ec1e4cb7fd81fe01e85419238a9cfb9d930c9</id>
<content type='text'>
Provide devlink documentation for three eswitch attributes:
mode, inline-mode, and encap-mode.

Signed-off-by: William Tu &lt;witu@nvidia.com&gt;
Reviewed-by: Jakub Kicinski &lt;kuba@kernel.org&gt;
Link: https://lore.kernel.org/r/20240325181228.6244-1-witu@nvidia.com
Signed-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;
</content>
</entry>
<entry>
<title>docs: fix info about representor identification</title>
<updated>2023-10-14T00:30:00Z</updated>
<author>
<name>Mateusz Polchlopek</name>
</author>
<published>2023-10-12T12:31:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a258c804aa8742763dce694b5e992d7ccf4294f2'/>
<id>urn:sha1:a258c804aa8742763dce694b5e992d7ccf4294f2</id>
<content type='text'>
Update the "How are representors identified?" documentation
subchapter. For newer kernels driver should use
SET_NETDEV_DEVLINK_PORT instead of ndo_get_devlink_port()
callback.

Fixes: 7712b3e966ea ("Merge branch 'net-fix-netdev-to-devlink_port-linkage-and-expose-to-user'")
Signed-off-by: Mateusz Polchlopek &lt;mateusz.polchlopek@intel.com&gt;
Reviewed-by: Wojciech Drewek &lt;wojciech.drewek@intel.com&gt;
Reviewed-by: Przemek Kitszel &lt;przemyslaw.kitszel@intel.com&gt;
Reviewed-by: Edward Cree &lt;ecree.xilinx@gmail.com&gt;
Link: https://lore.kernel.org/r/20231012123144.15768-1-mateusz.polchlopek@intel.com
Signed-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;
</content>
</entry>
<entry>
<title>docs: net: add an explanation of VF (and other) Representors</title>
<updated>2022-09-21T14:31:38Z</updated>
<author>
<name>Edward Cree</name>
</author>
<published>2022-09-05T13:55:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6fb4825e492b07ba6e450e5c9add3a35aa337f54'/>
<id>urn:sha1:6fb4825e492b07ba6e450e5c9add3a35aa337f54</id>
<content type='text'>
There's no clear explanation of what VF Representors are for, their
 semantics, etc., outside of vendor docs and random conference slides.
Add a document explaining Representors and defining what drivers that
 implement them are expected to do.

Signed-off-by: Edward Cree &lt;ecree.xilinx@gmail.com&gt;
Reviewed-by: Bagas Sanjaya &lt;bagasdotme@gmail.com&gt;
Link: https://lore.kernel.org/r/20220905135557.39233-1-ecree@xilinx.com
Signed-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;
</content>
</entry>
</feed>
