Re: [PATCH v3] stmmac: enable rx queues

Às 6:26 PM de 12/21/2016, David Miller escreveu: > From: Joao Pinto > Date: Tue, 20 Dec 2016 17:09:28 + > >> When the hardware is synthesized with multiple queues, all queues are >> disabled for default. This patch adds the rx queues configuration. >> This patch was

Re: [PATCH 2/2] net: wireless: fix to uses struct

On 21-12-2016 23:23, Ozgur Karatas wrote: > > The patch fixed to struct uses in reg.c, I think doesn't need to be use to > "struct". > There is dataype not have to logical link and each is different definitons. > > I'm undecided on this patch. I compiled and didn't to errors. There must be

PROBLEM:

[1] One line summary of the problem: Network scanner not detected by xsane after kernel upgrade [2] Full description of the problem/report: The scanner on my 'Epson WF-3520' multi-function is no longer detected by xsane (and other scan apps.) when connected wirelessly to the network. The

[PATCH iproute2 0/2] Fix the usage of TC tunnel key

Add dest UDP port parameter to the usage of tc tunnle key action and classifcation. Hadar Hen Zion (2): tc/cls_flower: Add to the usage encapsulation dest UDP port tc/m_tunnel_key: Add to the usage encapsulation dest UDP port tc/f_flower.c | 5 +++-- tc/m_tunnel_key.c | 2 +- 2 files

[PATCH iproute2 2/2] tc/m_tunnel_key: Add to the usage encapsulation dest UDP port

tunnel key set parameters includes also dest UDP port, add it to the usage. Fixes: 449c709c3868 ("tc/m_tunnel_key: Add dest UDP port to tunnel key action") Signed-off-by: Hadar Hen Zion Reported-by: Simon Horman --- tc/m_tunnel_key.c | 2 +- 1

[PATCH iproute2 1/2] tc/cls_flower: Add to the usage encapsulation dest UDP port

Encapsulation dest UDP port is part of the classifier matching parameters, add it to the usage. Fixes: 41aa17ff4668 ("tc/cls_flower: Add dest UDP port to tunnel params") Signed-off-by: Hadar Hen Zion Reported-by: Simon Horman --- tc/f_flower.c |

Re: George's crazy full state idea (Re: HalfSipHash Acceptable Usage)

> True, but it's called get_random_int(), and it seems like making it > stronger, especially if the performance cost is low to zero, is a good > thing. If it's cheap enough, I don't mind. But it's documented as being marginal-quality, used where speed is more important. In particular, it's

<    1   2