<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/ethernet/amd/xgbe, branch linux-4.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2019-11-25T14:54:05Z</updated>
<entry>
<title>net: amd: fix return type of ndo_start_xmit function</title>
<updated>2019-11-25T14:54:05Z</updated>
<author>
<name>YueHaibing</name>
</author>
<published>2018-09-19T10:50:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=945536fb45e8914f139ab381dd1e1ac8b82000b9'/>
<id>urn:sha1:945536fb45e8914f139ab381dd1e1ac8b82000b9</id>
<content type='text'>
[ Upstream commit fe72352e37ae8478f4c97975a9831f0c50f22e73 ]

The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
which is a typedef for an enum type, so make sure the implementation in
this driver has returns 'netdev_tx_t' value, and change the function
return type to netdev_tx_t.

Found by coccinelle.

Signed-off-by: YueHaibing &lt;yuehaibing@huawei.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>net: fix amd-xgbe flow-control issue</title>
<updated>2018-08-06T14:24:40Z</updated>
<author>
<name>tangpengpeng</name>
</author>
<published>2018-07-26T06:45:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3c3deb06ebda981b65be2abfd5980e23b1519dff'/>
<id>urn:sha1:3c3deb06ebda981b65be2abfd5980e23b1519dff</id>
<content type='text'>
[ Upstream commit 7f3fc7ddf719cd6faaf787722c511f6918ac6aab ]

If we enable or disable xgbe flow-control by ethtool ,
it does't work.Because the parameter is not properly
assigned,so we need to adjust the assignment order
of the parameters.

Fixes: c1ce2f77366b ("amd-xgbe: Fix flow control setting logic")
Signed-off-by: tangpengpeng &lt;tangpengpeng@higon.com&gt;
Acked-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>amd-xgbe: Fix unused suspend handlers build warning</title>
<updated>2018-02-25T10:03:46Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2016-11-26T20:53:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=91e017896dc5e7417e164733a3c97de02b14adaa'/>
<id>urn:sha1:91e017896dc5e7417e164733a3c97de02b14adaa</id>
<content type='text'>
commit 91eefaabf102c539e6f5531e9a1e5ed46d2b41ca upstream.

Fix:

  drivers/net/ethernet/amd/xgbe/xgbe-main.c:835:12: warning: ‘xgbe_suspend’ defined
    but not used [-Wunused-function]
  drivers/net/ethernet/amd/xgbe/xgbe-main.c:855:12: warning: ‘xgbe_resume’ defined
    but not used [-Wunused-function]

I see it during randconfig builds here.

Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;
Cc: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Cc: netdev@vger.kernel.org
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>amd-xgbe: Check xgbe_init() return code</title>
<updated>2017-07-05T12:37:19Z</updated>
<author>
<name>Lendacky, Thomas</name>
</author>
<published>2017-01-20T18:14:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3d2cbbcbde3d755b012dfce8115b35f53408f648'/>
<id>urn:sha1:3d2cbbcbde3d755b012dfce8115b35f53408f648</id>
<content type='text'>
[ Upstream commit 738f7f647371ff4cfc9646c99dba5b58ad142db3 ]

The xgbe_init() routine returns a return code indicating success or
failure, but the return code is not checked. Add code to xgbe_init()
to issue a message when failures are seen and add code to check the
xgbe_init() return code.

Signed-off-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@verizon.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>amd-xgbe: Fix jumbo MTU processing on newer hardware</title>
<updated>2017-03-30T07:35:13Z</updated>
<author>
<name>Lendacky, Thomas</name>
</author>
<published>2017-03-15T20:11:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ae43f9360a21b35cf785ae9a0fdce524d7af0938'/>
<id>urn:sha1:ae43f9360a21b35cf785ae9a0fdce524d7af0938</id>
<content type='text'>
[ Upstream commit 622c36f143fc9566ba49d7cec994c2da1182d9e2 ]

Newer hardware does not provide a cumulative payload length when multiple
descriptors are needed to handle the data. Once the MTU increases beyond
the size that can be handled by a single descriptor, the SKB does not get
built properly by the driver.

The driver will now calculate the size of the data buffers used by the
hardware.  The first buffer of the first descriptor is for packet headers
or packet headers and data when the headers can't be split. Subsequent
descriptors in a multi-descriptor chain will not use the first buffer. The
second buffer is used by all the descriptors in the chain for payload data.
Based on whether the driver is processing the first, intermediate, or last
descriptor it can calculate the buffer usage and build the SKB properly.

Tested and verified on both old and new hardware.

Signed-off-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>amd-xgbe: fix a couple timeout loops</title>
<updated>2015-12-15T17:43:01Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2015-12-15T10:12:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c7557e6a56510ff6636d40ad4ff64a3ef7d9e197'/>
<id>urn:sha1:c7557e6a56510ff6636d40ad4ff64a3ef7d9e197</id>
<content type='text'>
At the end of the loop we test "if (!count)" but because "count--" is
a post-op then the loop will end with count set to -1.  I have fixed
this by changing it to --count.

Fixes: c5aa9e3b8156 ('amd-xgbe: Initial AMD 10GbE platform driver')
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'acpi-pci'</title>
<updated>2015-11-07T00:30:10Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2015-11-07T00:30:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f2115faaf0df42623638dfbfc5bdaab6ef7375ab'/>
<id>urn:sha1:f2115faaf0df42623638dfbfc5bdaab6ef7375ab</id>
<content type='text'>
* acpi-pci:
  PCI: ACPI: Add support for PCI device DMA coherency
  PCI: OF: Move of_pci_dma_configure() to pci_dma_configure()
  of/pci: Fix pci_get_host_bridge_device leak
  device property: ACPI: Remove unused DMA APIs
  device property: ACPI: Make use of the new DMA Attribute APIs
  device property: Adding DMA Attribute APIs for Generic Devices
  ACPI: Adding DMA Attribute APIs for ACPI Device
  device property: Introducing enum dev_dma_attr
  ACPI: Honor ACPI _CCA attribute setting

Conflicts:
	drivers/crypto/ccp/ccp-platform.c
</content>
</entry>
<entry>
<title>device property: ACPI: Make use of the new DMA Attribute APIs</title>
<updated>2015-11-07T00:29:22Z</updated>
<author>
<name>Suthikulpanit, Suravee</name>
</author>
<published>2015-10-28T22:50:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1831eff876bd0bb8d64e9965a7ff47486c9a3ecd'/>
<id>urn:sha1:1831eff876bd0bb8d64e9965a7ff47486c9a3ecd</id>
<content type='text'>
Now that we have the new DMA attribute APIs, we can replace the older
acpi_check_dma() and device_dma_is_coherent().

Signed-off-by: Suravee Suthikulpanit &lt;Suravee.Suthikulpanit@amd.com&gt;
Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;
Reviewed-by: Hanjun Guo &lt;hanjun.guo@linaro.org&gt;
Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2015-11-01T04:15:30Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2015-11-01T04:15:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b75ec3af27bf011a760e2f44eb25a99b6fbb0fb3'/>
<id>urn:sha1:b75ec3af27bf011a760e2f44eb25a99b6fbb0fb3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>amd-xgbe: Fix race between access of desc and desc index</title>
<updated>2015-10-28T02:49:22Z</updated>
<author>
<name>Lendacky, Thomas</name>
</author>
<published>2015-10-26T22:13:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=20986ed826cbb36bb8f2d77f872e3c52d8d30647'/>
<id>urn:sha1:20986ed826cbb36bb8f2d77f872e3c52d8d30647</id>
<content type='text'>
During Tx cleanup it's still possible for the descriptor data to be
read ahead of the descriptor index. A memory barrier is required between
the read of the descriptor index and the start of the Tx cleanup loop.
This allows a change to a lighter-weight barrier in the Tx transmit
routine just before updating the current descriptor index.

Since the memory barrier does result in extra overhead on arm64, keep
the previous change to not chase the current descriptor value. This
prevents the execution of the barrier for each loop performed.

Suggested-by: Alexander Duyck &lt;alexander.duyck@gmail.com&gt;
Signed-off-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
