<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/ethernet/emulex, branch linux-4.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-01-22T21:22:42Z</updated>
<entry>
<title>be2net: restore properly promisc mode after queues reconfiguration</title>
<updated>2018-01-22T21:22:42Z</updated>
<author>
<name>Ivan Vecera</name>
</author>
<published>2018-01-19T19:23:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=52acf06451930eb4cefabd5ecea56e2d46c32f76'/>
<id>urn:sha1:52acf06451930eb4cefabd5ecea56e2d46c32f76</id>
<content type='text'>
The commit 622190669403 ("be2net: Request RSS capability of Rx interface
depending on number of Rx rings") modified be_update_queues() so the
IFACE (HW representation of the netdevice) is destroyed and then
re-created. This causes a regression because potential promiscuous mode
is not restored properly during be_open() because the driver thinks
that the HW has promiscuous mode already enabled.

Note that Lancer is not affected by this bug because RX-filter flags are
disabled during be_close() for this chipset.

Cc: Sathya Perla &lt;sathya.perla@broadcom.com&gt;
Cc: Ajit Khaparde &lt;ajit.khaparde@broadcom.com&gt;
Cc: Sriharsha Basavapatna &lt;sriharsha.basavapatna@broadcom.com&gt;
Cc: Somnath Kotur &lt;somnath.kotur@broadcom.com&gt;

Fixes: 622190669403 ("be2net: Request RSS capability of Rx interface depending on number of Rx rings")
Signed-off-by: Ivan Vecera &lt;ivecera@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>locking/atomics: COCCINELLE/treewide: Convert trivial ACCESS_ONCE() patterns to READ_ONCE()/WRITE_ONCE()</title>
<updated>2017-10-25T09:01:08Z</updated>
<author>
<name>Mark Rutland</name>
</author>
<published>2017-10-23T21:07:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6aa7de059173a986114ac43b8f50b297a86f09a8'/>
<id>urn:sha1:6aa7de059173a986114ac43b8f50b297a86f09a8</id>
<content type='text'>
Please do not apply this to mainline directly, instead please re-run the
coccinelle script shown below and apply its output.

For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't harmful, and changing them results in
churn.

However, for some features, the read/write distinction is critical to
correct operation. To distinguish these cases, separate read/write
accessors must be used. This patch migrates (most) remaining
ACCESS_ONCE() instances to {READ,WRITE}_ONCE(), using the following
coccinelle script:

----
// Convert trivial ACCESS_ONCE() uses to equivalent READ_ONCE() and
// WRITE_ONCE()

// $ make coccicheck COCCI=/home/mark/once.cocci SPFLAGS="--include-headers" MODE=patch

virtual patch

@ depends on patch @
expression E1, E2;
@@

- ACCESS_ONCE(E1) = E2
+ WRITE_ONCE(E1, E2)

@ depends on patch @
expression E;
@@

- ACCESS_ONCE(E)
+ READ_ONCE(E)
----

Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@linux.vnet.ibm.com&gt;
Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Cc: davem@davemloft.net
Cc: linux-arch@vger.kernel.org
Cc: mpe@ellerman.id.au
Cc: shuah@kernel.org
Cc: snitzer@redhat.com
Cc: thor.thayer@linux.intel.com
Cc: tj@kernel.org
Cc: viro@zeniv.linux.org.uk
Cc: will.deacon@arm.com
Link: http://lkml.kernel.org/r/1508792849-3115-19-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;
</content>
</entry>
<entry>
<title>be2net: fix TSO6/GSO issue causing TX-stall on Lancer/BEx</title>
<updated>2017-09-13T16:28:18Z</updated>
<author>
<name>Suresh Reddy</name>
</author>
<published>2017-09-13T15:12:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=822f8565c93949fb2d31502d595c8bc45629c9b7'/>
<id>urn:sha1:822f8565c93949fb2d31502d595c8bc45629c9b7</id>
<content type='text'>
IPv6 TSO requests with extension hdrs are a problem to the
Lancer and BEx chips. Workaround is to disable TSO6 feature
for such packets.

Also in Lancer chips, MSS less than 256 was resulting in TX stall.
Fix this by disabling GSO when MSS less than 256.

Signed-off-by: Suresh Reddy &lt;suresh.reddy@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>benet: fix set but not used warning</title>
<updated>2017-07-25T19:31:37Z</updated>
<author>
<name>stephen hemminger</name>
</author>
<published>2017-07-24T17:25:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8916829366c17a12c996a10da43c7f9d2e5e7039'/>
<id>urn:sha1:8916829366c17a12c996a10da43c7f9d2e5e7039</id>
<content type='text'>
warning: variable ‘netdev’ set but not used

Signed-off-by: Stephen Hemminger &lt;sthemmin@microsoft.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2017-05-27T00:46:35Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2017-05-27T00:46:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=34aa83c2fc23e055968387c8b78ac8bafd735aff'/>
<id>urn:sha1:34aa83c2fc23e055968387c8b78ac8bafd735aff</id>
<content type='text'>
Overlapping changes in drivers/net/phy/marvell.c, bug fix in 'net'
restricting a HW workaround alongside cleanups in 'net-next'.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>be2net: Update the driver version to 11.4.0.0</title>
<updated>2017-05-25T18:44:49Z</updated>
<author>
<name>Suresh Reddy</name>
</author>
<published>2017-05-25T02:24:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aab0830a3811fc242b8cdd82655e98ed5387cc6a'/>
<id>urn:sha1:aab0830a3811fc242b8cdd82655e98ed5387cc6a</id>
<content type='text'>
Signed-off-by: Suresh Reddy &lt;suresh.reddy@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>be2net: Fix UE detection logic for BE3</title>
<updated>2017-05-25T18:44:49Z</updated>
<author>
<name>Suresh Reddy</name>
</author>
<published>2017-05-25T02:24:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=673c96e5af99b6f8eab3ce37afa11cb28c14cf2f'/>
<id>urn:sha1:673c96e5af99b6f8eab3ce37afa11cb28c14cf2f</id>
<content type='text'>
On certain platforms BE3 chips may indicate spurious UEs (unrecoverable
error). Because of the UE detection logic was disabled in the driver
for BE3 chips. Because of this, even in cases of a real UE,
a failover will not occur. This patch re-enables UE detection on BE3
and if a UE is detected, reads the POST register. If the POST register,
reports either a FAT_LOG_STATE or a ARMFW_UE, then it means that a valid
UE occurred in the chip.

Signed-off-by: Suresh Reddy &lt;suresh.reddy@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>be2net: Fix offload features for Q-in-Q packets</title>
<updated>2017-05-24T20:27:14Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2017-05-23T17:38:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cc6e9de62a7f84c9293a2ea41bc412b55bb46e85'/>
<id>urn:sha1:cc6e9de62a7f84c9293a2ea41bc412b55bb46e85</id>
<content type='text'>
At least some of the be2net cards do not seem to be capabled
of performing checksum offload computions on Q-in-Q packets.
In these case, the recevied checksum on the remote is invalid
and TCP syn packets are dropped.

This patch adds a call to check disbled acceleration features
on Q-in-Q tagged traffic.

CC: Sathya Perla &lt;sathya.perla@broadcom.com&gt;
CC: Ajit Khaparde &lt;ajit.khaparde@broadcom.com&gt;
CC: Sriharsha Basavapatna &lt;sriharsha.basavapatna@broadcom.com&gt;
CC: Somnath Kotur &lt;somnath.kotur@broadcom.com&gt;
Signed-off-by: Vladislav Yasevich &lt;vyasevic@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>benet: Use time_before_eq for time comparison</title>
<updated>2017-05-01T15:12:46Z</updated>
<author>
<name>Karim Eshapa</name>
</author>
<published>2017-05-01T13:58:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2faf26575350e49c1e242b7a464e9302f78b9b15'/>
<id>urn:sha1:2faf26575350e49c1e242b7a464e9302f78b9b15</id>
<content type='text'>
Use time_before_eq for time comparison more safe and dealing
with timer wrapping to be future-proof.

Signed-off-by: Karim Eshapa &lt;karim.eshapa@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>be2net: VxLAN offload should be re-enabled when only 1 UDP port is left</title>
<updated>2017-04-18T19:56:25Z</updated>
<author>
<name>Sriharsha Basavapatna</name>
</author>
<published>2017-04-17T16:03:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bf8d9dfb9beeeef48f0444eb02198a09d5a52954'/>
<id>urn:sha1:bf8d9dfb9beeeef48f0444eb02198a09d5a52954</id>
<content type='text'>
We disable VxLAN offload when more than 1 UDP port is added to the driver,
since Skyhawk doesn't support offload with multiple ports. The existing
driver design expects the user to delete all port configurations and create
a configuration with a single UDP port for VxLAN offload to be re-enabled.
Remove this restriction by tracking the ports added and re-enabling offload
when ports get deleted and only 1 port is left.

Signed-off-by: Sriharsha Basavapatna &lt;sriharsha.basavapatna@broadcom.com&gt;
Reviewed-by: Sathya Perla &lt;sathya.perla@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
