Re: [PATCH net-next] tun: don't require serialization lock on tx

On Thu, Apr 14, 2016 at 06:39:39PM +0200, Paolo Abeni wrote: > The current tun_net_xmit() implementation don't need any external > lock since it relies on rcu protection for the tun data structure > and on socket queue lock for skb queuing. > > This patch set the NETIF_F_LLTX feature bit in the

[PATCH] macsec: fix crypto Kconfig dependency

The new MACsec driver uses the AES crypto algorithm, but can be configured even if CONFIG_CRYPTO is disabled, leading to a build error: warning: (MAC80211 && MACSEC) selects CRYPTO_GCM which has unmet direct dependencies (CRYPTO) warning: (BT && CEPH_LIB && INET && MAC802154 && MAC80211 &&

Нужны дилеры для кухонной мебели. Скидка - ЗO%.

Добрый день. Меня зовут Наталья. Я представляю мебельную фабрику. Наша фирма приглашает к сотрудничеству дилеров. Наша мебель торгуется в среднем ценовом сегменте. Цена нашей мебели для кухни в среднем на 2O-ЗО% ниже, чем на рынке: - Классические кухни - ЗЗ000 р. за 1 п/м - Кухни современные -

Re: linux-next: build failure after merge of the net-next tree

On Wednesday 13 April 2016 11:15:13 David Miller wrote: > From: Stephen Rothwell > Date: Wed, 13 Apr 2016 17:50:28 +1000 > > > After merging the net-next tree, today's linux-next build (arm > > allmodconfig) failed like thisi (this has actually been failing for a > > few

Re: [PATCH v3] prism54: isl_38xx: Replace 'struct timeval'

On Sun, 2016-04-17 at 01:34 +0200, Arnd Bergmann wrote: > On Wednesday 13 April 2016 10:38:26 Johannes Berg wrote: > > > > > > > > The patch was build-tested / debugged by removing the > > > "if VERBOSE > SHOW_ERROR_MESSAGES" guards. > > Stands to reason that we should just remove the (more or

bpf: use-after-free in array_map_alloc

Hi all, I've hit the following while fuzzing with syzkaller inside a KVM tools guest running the latest -next kernel: [ 2590.845375] == [ 2590.845445] BUG: KASAN: use-after-free in pcpu_extend_area_map+0x8a/0x130 at addr

[PATCH net-next v4 6/9] net: dsa: mv88e6xxx: add family to info

Add an mv88e6xxx_family enum to the info structure for better family indentification. Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn --- drivers/net/dsa/mv88e6123.c | 3 ++ drivers/net/dsa/mv88e6131.c | 4 +++

[PATCH net-next v4 4/9] net: dsa: mv88e6xxx: read switch ID in probe

Read the switch ID only once, at probe time, to avoid multiple read accesses and MII bus checking. Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn --- drivers/net/dsa/mv88e6xxx.c | 57 - 1

[PATCH net-next v4 9/9] net: dsa: mv88e6xxx: remove switch ID from ps

ps->id is not needed anymore, so remove it as well as the related defined values. Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn --- drivers/net/dsa/mv88e6xxx.c | 1 - drivers/net/dsa/mv88e6xxx.h | 32

[PATCH net-next v4 5/9] net: dsa: mv88e6xxx: add switch info

Add a new switch info structure which is meant to store switch models static information, such as product number, name, number of ports, number of databases, etc. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 15 +++

[PATCH net-next v4 8/9] net: dsa: mv88e6xxx: add number of db to info

Add the number of databases to the info structure. Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn --- drivers/net/dsa/mv88e6123.c | 3 +++ drivers/net/dsa/mv88e6131.c | 4 drivers/net/dsa/mv88e6171.c | 4

[PATCH net-next v4 3/9] net: dsa: mv88e6xxx: drop revision probing

There is no point in having a special case for the revision when probing a switch model. The code gets cluttered with unnecessary defines, and leads to errors when code such as mv88e6131_setup compares PORT_SWITCH_ID_6131_B2 to ps->id which masks the revision. Drop every revision definition, and

[PATCH net-next v4 1/9] net: dsa: constify probed name

Change the dsa_switch_driver.probe function to return a const char *. Signed-off-by: Vivien Didelot --- drivers/net/dsa/bcm_sf2.c | 6 +++--- drivers/net/dsa/mv88e6060.c | 10 +- drivers/net/dsa/mv88e6123.c | 6 +++--- drivers/net/dsa/mv88e6131.c

[PATCH net-next v4 0/9] net: dsa: mv88e6xxx: factorize switch info

This patchset factorizes the mv88e6xxx code by sharing a new extendable info structure to store static data such as switch family, product number, number of ports, number of databases and the name. The next step is to add a "flags" bitmap member to the info structure in order to simplify the

Re: [PATCH net-next v3 2/8] net: dsa: mv88e6xxx: drop revision probing

On Sat, Apr 16, 2016 at 06:41:39PM -0400, Vivien Didelot wrote: > There is no point in having a special case for the revision when probing > a switch model. The code gets cluttered with unnecessary defines, and > leads to errors when code such as mv88e6131_setup compares > PORT_SWITCH_ID_6131_B2

Re: [PATCH net-next v3 3/8] net: dsa: mv88e6xxx: read switch ID in probe

On Sat, Apr 16, 2016 at 06:41:40PM -0400, Vivien Didelot wrote: > Read the switch ID only once, at probe time, to avoid multiple read > accesses and MII bus checking. > > Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn Thanks

Re: [PATCH net-next v3 4/8] net: dsa: mv88e6xxx: add switch info

Hi Andrew, Andrew Lunn writes: >> @@ -3100,16 +3100,19 @@ char *mv88e6xxx_drv_probe(struct device *dsa_dev, >> struct device *host_dev, >> prod_num = (id & 0xfff0) >> 4; >> rev = id & 0x000f; >> >> -name = mv88e6xxx_lookup_name(id, table, num); >> -if

[RFC PATCH] net: ipv4: add l3 and l4 multipath algorithms

Hi all, I've been looking into adding both l3 and l4 multipath algorithms which are consistent in both forwarded and locally originated traffic. This attempt removes the old multipath code, and trades performance for unifying both locally originated and forwarded traffic cases. There's one case

Re: bpf: use-after-free in array_map_alloc

On Sun, Apr 17, 2016 at 12:58:21PM -0400, Sasha Levin wrote: > Hi all, > > I've hit the following while fuzzing with syzkaller inside a KVM tools guest > running the latest -next kernel: thanks for the report. Adding Tejun... if I read the report correctly it's not about bpf, but rather points

Re: FlameGraph of mlx4 early drop with order-0 pages

On Fri, Apr 15, 2016 at 09:40:34PM +0200, Jesper Dangaard Brouer wrote: > Hi Mel, > > I did an experiment that you might find interesting. Using Brenden's > early drop with eBPF in the mxl4 driver. I changed the mlx4 driver to > use order-0 pages. It usually use order-3 pages to amortize the

Re: [PATCH net-next v3 4/8] net: dsa: mv88e6xxx: add switch info

> @@ -3100,16 +3100,19 @@ char *mv88e6xxx_drv_probe(struct device *dsa_dev, > struct device *host_dev, > prod_num = (id & 0xfff0) >> 4; > rev = id & 0x000f; > > - name = mv88e6xxx_lookup_name(id, table, num); > - if (!name) > + info = mv88e6xxx_lookup_info(prod_num,

[PATCH net-next v4 7/9] net: dsa: mv88e6xxx: add number of ports to info

Drop the ps->num_ports variable in favor of a new member of the info structure. This removes the need to assign it at setup time. Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn --- drivers/net/dsa/mv88e6123.c | 16 +++-

Re: FlameGraph of mlx4 early drop with order-0 pages

On Sun, 17 Apr 2016 14:23:57 +0100 Mel Gorman wrote: > > Signing off, heading for the plane soon... see you at MM-summit! > > Indeed and we'll slap some sort of plan together. If there is a slot free, > we might spend 15-30 minutes on it. Failing that, we'll grab

[PATCH net-next v4 2/9] net: dsa: mv88e6xxx: drop double ds assignment

Every driver assigns ps->ds even though it gets assigned in the shared mv88e6xxx_setup_common function. Kill redundancy. Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn --- drivers/net/dsa/mv88e6123.c | 2 --

Re: [PATCH net-next v4 5/9] net: dsa: mv88e6xxx: add switch info

On Sun, Apr 17, 2016 at 01:23:59PM -0400, Vivien Didelot wrote: > Add a new switch info structure which is meant to store switch models > static information, such as product number, name, number of ports, > number of databases, etc. > > Signed-off-by: Vivien Didelot

[PATCH net-next V2 10/11] net/mlx5e: Delay skb->data access

Move mlx5e_handle_csum and eth_type_trans to the end of mlx5e_build_rx_skb to gain some more time before accessing skb->data, to reduce cache misses. Signed-off-by: Saeed Mahameed --- drivers/net/ethernet/mellanox/mlx5/core/en_rx.c |7 +++ 1 files changed, 3

[PATCH net-next V2 09/11] net/mlx5e: Remove redundant barrier

From: Tariq Toukan The bit-op operation one line before is an explicit barrier by itself. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed --- drivers/net/ethernet/mellanox/mlx5/core/en_txrx.c |1 - 1 files changed,

[PATCH net-next V2 01/11] net/mlx5: Introduce device queue counters

From: Tariq Toukan A queue counter can collect several statistics for one or more hardware queues (QPs, RQs, etc ..) that the counter is attached to. For Ethernet it will provide an "out of buffer" counter which collects the number of all packets that are dropped due to

[PATCH net-next V2 05/11] net/mlx5e: Support RX multi-packet WQE (Striding RQ)

From: Tariq Toukan Introduce the feature of multi-packet WQE (RX Work Queue Element) referred to as (MPWQE or Striding RQ), in which WQEs are larger and serve multiple packets each. Every WQE consists of many strides of the same size, every received packet is aligned to a

[PATCH net-next V2 00/11] Mellanox 100G mlx5 driver receive path optimizations

Hello Dave, Changes from V1: - Rebased to efde611b0afa ("Merge branch 'nfp-next'") - Dropped: ("net/mlx5: Refactor mlx5_core_mr to mkey") Already merged into 4.6 from rdma tree. - Dropped: ("net/mlx5_core: Add ConnectX-5 to list of supported devices")

[PATCH net-next V2 08/11] net/mlx5e: Use napi_alloc_skb for RX SKB allocations

From: Tariq Toukan Instead of netdev_alloc_skb, we use the napi_alloc_skb function which is designated to allocate skbuff's for RX in a channel-specific NAPI instance, and implies the IP packet alignment. Signed-off-by: Tariq Toukan Signed-off-by:

[PATCH net-next V2 02/11] net/mlx5e: Allocate set of queue counters per netdev

From: Rana Shahout Connect all netdev RQs to this set of queue counters. Also, add an "rx_out_of_buffer" counter to ethtool, which indicates RX packet drops due to lack of receive buffers. Signed-off-by: Rana Shahout Signed-off-by: Tariq Toukan

[PATCH net-next V2 04/11] net/mlx5e: Use function pointers for RX data path handling

From: Tariq Toukan In preparation for Striding RQ feature, which will need its own RX handlers. This patch does not change any functionality. Signed-off-by: Tariq Toukan Signed-off-by: Achiad Shochat Signed-off-by: Saeed Mahameed

[PATCH net-next V2 06/11] net/mlx5e: Added ICO SQs

From: Tariq Toukan Added ICO (Internal Control Operations) SQ per channel to be used for driver internal operations such as memory registration for fragmented memory and nop requests upon ifconfig up. Signed-off-by: Tariq Toukan Signed-off-by: Saeed

[PATCH net-next V2 03/11] net/mlx5e: Use only close NUMA node for default RSS

From: Tariq Toukan Distribute default RSS table uniformly over the rings of the close NUMA node, instead of all available channels. This way we enforce the preference of close rings over far ones. Signed-off-by: Tariq Toukan Signed-off-by: Saeed

[PATCH net-next V2 07/11] net/mlx5e: Add fragmented memory support for RX multi packet WQE

From: Tariq Toukan If the allocation of a linear (physically continuous) MPWQE fails, we allocate a fragmented MPWQE. This is implemented via device's UMR (User Memory Registration) which allows to register multiple memory fragments into ConnectX hardware as a continuous

[PATCH net-next V2 11/11] net/mlx5e: Add ethtool counter for RX buffer allocation failures

From: Tariq Toukan Counts the number of RX buffer allocation failures and shows it in ethtool statistics. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed --- drivers/net/ethernet/mellanox/mlx5/core/en.h |8

Re: [PATCH net-next v4 1/9] net: dsa: constify probed name

On Sun, Apr 17, 2016 at 01:23:55PM -0400, Vivien Didelot wrote: > Change the dsa_switch_driver.probe function to return a const char *. > > Signed-off-by: Vivien Didelot Reviewed-by: Andrew Lunn Thanks Andrew > --- >

Re: FlameGraph of mlx4 early drop with order-0 pages

On Sun, Apr 17, 2016 at 07:24:32PM +0200, Jesper Dangaard Brouer wrote: > On Sun, 17 Apr 2016 14:23:57 +0100 > Mel Gorman wrote: > > > > Signing off, heading for the plane soon... see you at MM-summit! > > > > Indeed and we'll slap some sort of plan together. If

re:

I have a project request...

Re: [PATCH] net: ipv6: Do not fix up linklocal and loopback addresses

On 04/16/2016 07:26 PM, David Ahern wrote: > On 4/15/16 9:13 PM, Mike Manning wrote: >> f1705ec197e7 added the option to retain user configured addresses on an >> admin down. A comment to one of the later revisions suggested using the >> IFA_F_PERMANENT flag rather than adding a user_managed

[PATCH net-next 1/5] qed*: Align statistics names

There's a difference in statsitics' names starting at qed and propagating to qede, where egress counters indicate ranges while ingress counters indiciate high-end. Align all statistcs to follow the same conventions - name indicates range. Signed-off-by: Yuval Mintz ---

[PATCH net-next 5/5] qed*: Add support for read/write of eeprom

From: Sudarsana Reddy Kalluru Add the driver logic needed for supporting the ethtool APIs for reading and writing from the interface's eeprom. There's quite a bit of `magic' here [based on the ethtool `magic' field] which is retained by the user application

[PATCH net-next 0/5] qed*: eeprom access et al.

This patch series contains some ethtool-related enhancements, where the significant addition is the ability to read/write from the device's non-volatile memory via the ethtool socket [required for the adapter's fw-upgrade utility]. Dave, Please consider applying this to `net-next'. Thanks,

[PATCH net-next 4/5] qed: add support for link pause configuration.

From: Sudarsana Reddy Kalluru The APIs for making this sort of configuration [e.g., via ethtool] are already present in qede, but the current configuration flow in qed doesn't respect it. Signed-off-by: Sudarsana Reddy Kalluru

[PATCH net-next 2/5] qede: Add support for ethtool private flags

Adds a getter for the interfaces private flags. The only parameter currently supported is whether the interface is a coupled function [required for supporting 100g]. Signed-off-by: Yuval Mintz --- drivers/net/ethernet/qlogic/qede/qede_ethtool.c | 27

[PATCH net-next 3/5] qed*: Conditions for changing link

There's some inconsistency in current logic determining whether the link settings of a given interface can be changed; I.e., in all modes other than the so-called `deault' mode the interfaces are forbidden from changing the configuration - but even this rule is not applied to all user APIs that

Re: [PATCH v3] prism54: isl_38xx: Replace 'struct timeval'

On Sunday 17 April 2016 14:42:33 Johannes Berg wrote: > > I was thinking more restrictively of just the stuff that can't even be > built without modifying the sources - like the "#if VERBOSE" thing. All the DEBUG() statements are inside of this kind of check, so if we remove the #ifdefs, it

Re: [PATCH net-next v4 0/9] net: dsa: mv88e6xxx: factorize switch info

From: Vivien Didelot Date: Sun, 17 Apr 2016 13:23:54 -0400 > This patchset factorizes the mv88e6xxx code by sharing a new extendable > info structure to store static data such as switch family, product > number, number of ports, number of databases and the

Re: [PATCH net-next 5/5] qed*: Add support for read/write of eeprom

From: Yuval Mintz Date: Sun, 17 Apr 2016 22:26:35 +0300 > There's quite a bit of `magic' here [based on the ethtool `magic' > field] which is retained by the user application responsible for > interacting with the driver for the purpose of upgrading the nvram > image.

Re: linux-next: manual merge of the net-next tree with the net tree

On Mon, 2016-04-18 at 11:31 +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > net/ipv4/udp.c > > between commit: > > d894ba18d4e4 ("soreuseport: fix ordering for mixed v4/v6 sockets") > > from the net tree and commit: > >

Re: [PATCHv2] wlcore: spi: add wl18xx support

On Sunday 10 April 2016 07:37:23 Reizer, Eyal wrote: > Add support for using with both wl12xx and wl18xx. > > - all wilink family needs special init command for entering wspi mode. > extra clock cycles should be sent after the spi init command while the > cs pin is high. > - switch to

[PATCH net-next 2/2] bpf: add event output helper for notifications/sampling/logging

This patch adds a new helper for cls/act programs that can push events to user space applications. For networking, this can be f.e. for sampling, debugging, logging purposes or pushing of arbitrary wake-up events. The idea is similar to a43eec304259 ("bpf: introduce bpf_perf_event_output()

[PATCH net-next 1/2] bpf, trace: add BPF_F_CURRENT_CPU flag for bpf_perf_event_output

Add a BPF_F_CURRENT_CPU flag to optimize the use-case where user space has per-CPU ring buffers and the eBPF program pushes the data into the current CPU's ring buffer which saves us an extra helper function call in eBPF. Also, make sure to properly reserve the remaining flags which are not used.

Re: [PATCH net-next 2/2] bpf: add event output helper for notifications/sampling/logging

Hi Daniel, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-trace-add-BPF_F_CURRENT_CPU-flag-for-bpf_perf_event_output/20160418-063147 config: m68k-allyesconfig (attached as .config) reproduce: wget

[PATCH net-next 0/2] BPF updates

This minor set adds a new helper bpf_skb_event_output() for eBPF cls/act program types which allows to pass events to user space applications. For details, please see individual patches. Thanks! Daniel Borkmann (2): bpf, trace: add BPF_F_CURRENT_CPU flag for bpf_perf_event_output bpf: add

Re: bpf: use-after-free in array_map_alloc

On 04/17/2016 01:29 PM, Alexei Starovoitov wrote: > On Sun, Apr 17, 2016 at 12:58:21PM -0400, Sasha Levin wrote: >> > Hi all, >> > >> > I've hit the following while fuzzing with syzkaller inside a KVM tools >> > guest >> > running the latest -next kernel: > thanks for the report. Adding Tejun...

Re: [PATCH] macsec: fix crypto Kconfig dependency

From: Arnd Bergmann Date: Sun, 17 Apr 2016 11:19:55 +0200 > The new MACsec driver uses the AES crypto algorithm, but can be configured > even if CONFIG_CRYPTO is disabled, leading to a build error: > > warning: (MAC80211 && MACSEC) selects CRYPTO_GCM which has unmet direct >

Re: [PATCH net-next V2 05/11] net/mlx5e: Support RX multi-packet WQE (Striding RQ)

On Mon, 2016-04-18 at 00:31 +0300, Saeed Mahameed wrote: > Performance tested on ConnectX4-Lx 50G. > To isolate the feature under test, the numbers below were measured with > HW LRO turned off. We verified that the performance just improves when > LRO is turned back on. > > * Netperf single TCP

Re: [PATCH net] net: bcmgenet: device stats are unsigned long

Le 15/04/2016 10:47, Eric Dumazet a écrit : > From: Eric Dumazet > > On 64bit kernels, device stats are 64bit wide, not 32bit. > > Fixes: 1c1008c793fa4 ("net: bcmgenet: add main driver file") > Signed-off-by: Eric Dumazet > Cc: Florian Fainelli

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/ipv4/udp.c between commit: d894ba18d4e4 ("soreuseport: fix ordering for mixed v4/v6 sockets") from the net tree and commit: ca065d0cf80f ("udp: no longer use SLAB_DESTROY_BY_RCU") from the net-next tree. I

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/dsa/mv88e6xxx.c between commit: 207afda1b503 ("net: dsa: mv88e6xxx: share the same default FDB") from the net tree and commit: 009a2b9843bf ("net: dsa: mv88e6xxx: add number of ports to info") from

Re: [PATCH] ixgbe: use msleep for long delays

From: Arnd Bergmann Date: Sat, 16 Apr 2016 22:35:08 +0200 > The newly added x550em_a support causes a link failure on ARM because of > an overly long time passed into udelay(): > > ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined! > > There are

Re: [PATCH] bpf: avoid warning for wrong pointer cast

From: Arnd Bergmann Date: Sat, 16 Apr 2016 22:29:33 +0200 > Two new functions in bpf contain a cast from a 'u64' to a > pointer. This works on 64-bit architectures but causes a warning > on all 32-bit architectures: > > kernel/trace/bpf_trace.c: In function

RE: [PATCH net-next 5/5] qed*: Add support for read/write of eeprom

> > There's quite a bit of `magic' here [based on the ethtool `magic' > > field] which is retained by the user application responsible for > > interacting with the driver for the purpose of upgrading the nvram > > image. > > This is not how the 'magic' value of the eeprom structure is specified

[PATCH net-next V2 0/2] ethernet: intel: Support Hyper-V hosts

Make adjustments to the Intel 10G VF driver to support running on Hyper-V hosts. K. Y. Srinivasan (2): ethernet: intel: Add the device ID's presented while running on Hyper-V intel: ixgbevf: Support Windows hosts (Hyper-V) drivers/net/ethernet/intel/ixgbevf/defines.h |5 +

Re: [PATCH net-next 5/5] qed*: Add support for read/write of eeprom

From: Yuval Mintz Date: Mon, 18 Apr 2016 03:59:42 + > The third option I see is to completely ditch this, stating that although > We obviously CAN set the non-volatile memory we CAN'T do it with the > regular API, and to move into doing this via some proprietary API

[PATCH net-next v4] rtnetlink: add new RTM_GETSTATS message to dump link stats

From: Roopa Prabhu This patch adds a new RTM_GETSTATS message to query link stats via netlink from the kernel. RTM_NEWLINK also dumps stats today, but RTM_NEWLINK returns a lot more than just stats and is expensive in some cases when frequent polling for stats from

[PATCH net-next V2 0/2] ethernet: intel: Support Hyper-V hosts

Make adjustments to the Intel 10G VF driver to support running on Hyper-V hosts. K. Y. Srinivasan (2): ethernet: intel: Add the device ID's presented while running on Hyper-V intel: ixgbevf: Support Windows hosts (Hyper-V) drivers/net/ethernet/intel/ixgbevf/defines.h |5 +

[PATCH net-next V2 1/2] ethernet: intel: Add the device ID's presented while running on Hyper-V

Intel SR-IOV cards present different ID when running on Hyper-V. Add the device IDs presented while running on Hyper-V. Signed-off-by: K. Y. Srinivasan --- V2: No change from V1. drivers/net/ethernet/intel/ixgbevf/defines.h |5 + 1 files changed, 5

[PATCH net-next V2 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V)

On Hyper-V, the VF/PF communication is a via software mediated path as opposed to the hardware mailbox. Make the necessary adjustments to support Hyper-V. Signed-off-by: K. Y. Srinivasan --- V2: Addressed most of the comments from Alexander Duyck

Re: [PATCH V2] net: ethernet: mellanox: correct page conversion

From: Sinan Kaya Date: Sat, 16 Apr 2016 18:23:32 -0400 > Current code is assuming that the address returned by dma_alloc_coherent > is a logical address. This is not true on ARM/ARM64 systems. This patch > replaces dma_alloc_coherent with dma_map_page API. The address

Re: [PATCH] of_mdio: make of_mdiobus_register_{device|phy}() *void*

From: Sergei Shtylyov Date: Sun, 17 Apr 2016 01:05:19 +0300 > The results of of_mdiobus_register_{device|phy}() are never checked, so we > can make both these functions *void*... > > Signed-off-by: Sergei Shtylyov

Re: [PATCH V2] net: ethernet: mellanox: correct page conversion

On 2016-04-18 00:00, David Miller wrote: From: Sinan Kaya Date: Sat, 16 Apr 2016 18:23:32 -0400 Current code is assuming that the address returned by dma_alloc_coherent is a logical address. This is not true on ARM/ARM64 systems. This patch replaces dma_alloc_coherent

RE: [PATCHv2] wlcore: spi: add wl18xx support

> > > > - all wilink family needs special init command for entering wspi mode. > > extra clock cycles should be sent after the spi init command while the > > cs pin is high. > > - switch to controling the cs pin from the spi driver for achieveing the > > above. > > - the selected cs gpio is