> Currently ethtool implementation does not have a way to pass the metadata for
> eeprom related operations. Some adapters have a complicated non-volatile
> memory implementation that requires additional information – there are drivers
> [bnx2x and bnxt] that use the ‘magic’ field in the
The current code only disables those IRQs that we will later use. To
ensure that we have a predefined state, we really want to disable all IRQs.
Change the code to disable all IRQs to achieve this.
Signed-off-by: John Crispin
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c |
On Sat, 2016-06-04 at 16:43 -0300, Augusto Mecking Caringi wrote:
> On Sat, Jun 4, 2016 at 4:01 PM, Colin King wrote:
> > From: Colin Ian King
> > trivial fix to spelling mistake in pr_err message
[]
> > diff --git
The QDMA engine can fail to update the register pointing to the next TX
descriptor if this bit does not get set in the QDMA configuration register.
Not setting this bit can result in invalid values inside the TX rings
registers which will causes TX stalls.
Signed-off-by: John Crispin
During stress testing, after reducing the threshold value, we have seen
TX timeouts that were caused by the watchdog_timeo value being too low.
Increase the value to 5 * HZ which is a value commonly used by many other
drivers.
Signed-off-by: John Crispin
---
Scratch memory gets allocated in mtk_init_fq_dma() but the corresponding
code to free it is missing inside mtk_dma_free() causing a memory leak.
With this patch applied, we can run ifconfig up/down several thousand
times without any problems.
Signed-off-by: John Crispin
---
The logic to calculate the threshold value for stopping the TX queue is
bad. Currently it will always use 1/2 of the rings size, which is way too
much. Set the threshold to MAX_SKB_FRAGS. This makes sure that the queue
is stopped when there is not enough room to accept an additional segment.
This series contains various small fixes that we stumbled across while
doing thorough testing and code level reviewing of the driver. The only
patch that sticks out is the first one, which addresses a DQL related
issue. The rest are just minor fixes.
John Crispin (12):
net: mediatek: fix DQL
The lookup of the tx_buffer in the error path inside mtk_tx_map() uses the
wrong descriptor pointer. This looks like a copy & paste error. Change the
code to use the correct pointer.
Signed-off-by: John Crispin
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c |2 +-
1 file
There are two places inside mtk_poll_rx where rx_dropped is not being
incremented properly. Fix this by adding the missing code to increment
the counter.
Signed-off-by: John Crispin
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c |2 ++
1 file changed, 2 insertions(+)
From: John Crispin
Date: Sun, 5 Jun 2016 08:32:54 +0200
> @@ -625,7 +625,16 @@ static int mtk_tx_map(struct sk_buff *skb, struct
> net_device *dev,
> WRITE_ONCE(itxd->txd3, (TX_DMA_SWC | TX_DMA_PLEN0(skb_headlen(skb)) |
> (!nr_frags *
From: Zhu Yanjun
Signed-off-by: Zhu Yanjun
---
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
On Sat, Jun 04, 2016 at 08:54:00PM +0530, Bhaktipriya Shridhar wrote:
> diff --git a/drivers/net/ethernet/cavium/liquidio/request_manager.c
> b/drivers/net/ethernet/cavium/liquidio/request_manager.c
> index a2a2465..9313915 100644
> --- a/drivers/net/ethernet/cavium/liquidio/request_manager.c
>
The code checks if the queue should be stopped because we are below the
threshold of free descriptors only to check if it should be started again.
If we do end up in a state where we are at the threshold limit, it makes
more sense to just stop the queue and wait for the next IRQ to trigger the
TX
Hi Florian,
Fri, Jun 03, 2016 at 12:39:45PM IDT, ido...@mellanox.com wrote:
>Commit 8626c56c8279 ("bridge: fix potential use-after-free when hook
>returns QUEUE or STOLEN verdict") fixed incorrect usage of NF_HOOK's
>return value by consuming packets in okfn via br_pass_frame_up().
>
>However,
On 06/05/2016 01:46 AM, kbuild test robot wrote:
Hi,
[auto build test ERROR on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Zi-Shen-Lim/arm64-bpf-implement-bpf_tail_call-helper/20160605-060435
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc
On Sat, Jun 04, 2016 at 07:29:01PM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> In if_sdio.c, the workqueue card->workqueue has workitem
> >packet_worker, which is mapped to if_sdio_host_to_card_worker.
> The workitem is involved in sending
On Sun, 2016-06-05 at 17:14 +0800, zyjzyj2...@gmail.com wrote:
> From: Zhu Yanjun
>
>
> Signed-off-by: Zhu Yanjun
> ---
You do not explain if this is a bug fix (targeting net tree) or simply
an optimization in the slow path (targeting net-next tree)
> > Since implementing VLAN filtering in commit 05cc5a39ddb74
> > ("bnx2x: add vlan filtering offload") bnx2x refuses to add a VLAN
> > while the interface is down.
>
> Hi Michal - thanks; I'll review this one on Sunday.
I'm a bit worried about the fact we're hiding actual issues -
E.g., if for
Hi,all
I am using the ixgbe nic. I found that the rtnl_lock is being
used to enable upper device, such as macvlan. I am curious
why rcu_read_lock is not used here.
I replaced rtnl_lock with rcu_read_lock here. Then I made tests and
it can work well.
So can the rtnl_lock be replaced with
From: Ian Campbell
commit dedc58e067d8c379a15a8a183c5db318201295bb upstream.
The peer may be expecting a reply having sent a request and then done a
shutdown(SHUT_WR), so tearing down the whole socket at this point seems
wrong and breaks for me with a client which does
Today, the VF is aware of its queues context-ids, and calculates the
doorbell address when opening its queues on its own.
The configuration of doorbells in HW can sometime in the future be changed
by the PF [hw has several configurable features that might affect doorbell
addresses, e.g., dpm
One of the goals of the vf's first message to the PF [acquire]
is to learn about the number of resources available to it [macs, vlans,
etc.]. This is done via negotiation - the VF requires a set of resources,
which the PF either approves or disaproves and sends a smaller set of
resources as
In order for VFs to work, current implementation demands that the VF's
requried storm firmware would be exactly the version that was loaded by
the PF, which is a very harsh requirement.
This patch series is intended to relax this -
the recently submitted firmware is intended to be forward/backward
Current driver require an exact match between VF and PF storm firmware;
Any difference would fail the VF acquire message, causing the VF probe
to be aborted.
While there's still dependencies between the two, the recent FW submission
has relaxed the match requirement - instead of an exact match,
On Sat, Jun 04, 2016 at 08:21:40PM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workitem viz
> (>wk.work which maps to oct_poll_req_completion) is involved
> in normal device operation.
On 16-06-04 12:24 PM, Daniel Borkmann wrote:
Add a possibility where the user can just specify the parent and
all filters under that parent are then being purged. Currently,
for example for scripting, one needs to specify pref/prio to have
a well-defined number for 'tc filter del' command for
Hello.
On 6/4/2016 7:24 PM, Daniel Borkmann wrote:
Add a possibility where the user can just specify the parent and
all filters under that parent are then being purged. Currently,
for example for scripting, one needs to specify pref/prio to have
a well-defined number for 'tc filter del'
> Acked-by: Daniel Borkmann
>
> [ Cc Willem: I believe we also need something similar for PACKET_FANOUT_DATA
> when PACKET_FANOUT_CBPF is requested since we have the same issue with the
> pointer in struct sock_fprog there, too. ]
Indeed. I'll send a patch in a few days
From: Lucas Bates
Signed-off-by: Lucas Bates
Signed-off-by: Jamal Hadi Salim
Acked-by: Phil Sutter
---
man/man8/tc-ife.8 | 117 ++
1 file changed, 117 insertions(+)
From: Amir Vadai
In order to make a filter processed only by hardware, skip_sw flag
should be supplied. This is an addition to the already existing skip_hw
flag (filter will be processed by software only). If no flag is
specified, filter will be processed by both software
On Sun, Jun 05, 2016 at 08:33:02AM +0200, John Crispin wrote:
> During stress testing, after reducing the threshold value, we have seen
> TX timeouts that were caused by the watchdog_timeo value being too low.
> Increase the value to 5 * HZ which is a value commonly used by many other
> drivers.
Commit 99aded71b52cfdfa22721c42e42efdd13a02f0a6 ("Staging: drivers: rtl8188eu:
use sizeof(*ptr) instead of sizeof(struct)") introduces an error in that the
sizeof(struct hal_data_8188e) is 18712, while the sizeof(*adapt->HalData) is
only 1! As a result, the system panics.
Fixes:
When this driver preallocates some SKBs, kmemleak is unable to find that
allocated memory when it scans. When the driver is unloaded, that memory
is released; therefore, the report is a false positive.
Signed-off-by: Larry Finger
---
On Sun, 2016-06-05 at 10:16 +, Yuval Mintz wrote:
> >
> > Currently ethtool implementation does not have a way to pass the metadata
> > for
> > eeprom related operations. Some adapters have a complicated non-volatile
> > memory implementation that requires additional information – there are
On Mon, May 30, 2016 at 11:41:22PM +0200, Lino Sanfilippo wrote:
>
> Did you see the same issues with the patch before (the one that, as you wrote,
> survived a whole night of stress testing)?
>
> Lino
Hi Lino,
Sorry for my late reply. I retested the previous patch, it did have
the same issue.
> > > Currently ethtool implementation does not have a way to pass the
> > > metadata for eeprom related operations. Some adapters have a
> > > complicated non-volatile memory implementation that requires
> > > additional information – there are drivers [bnx2x and bnxt] that use
> > > the ‘magic’
From: Jamal Hadi Salim
Signed-off-by: Jamal Hadi Salim
---
include/net/act_api.h| 8
net/sched/act_bpf.c | 6 +-
net/sched/act_connmark.c | 5 +
net/sched/act_csum.c | 6 ++
net/sched/act_gact.c | 5 +
From: Jamal Hadi Salim
Useful to know when the action was first used for accounting
(and debugging)
Signed-off-by: Jamal Hadi Salim
---
include/net/act_api.h| 2 ++
include/uapi/linux/pkt_cls.h | 1 +
net/sched/act_api.c | 1 +
From: Jamal Hadi Salim
Signed-off-by: Jamal Hadi Salim
---
include/net/act_api.h | 14 --
include/net/tc_act/tc_defact.h | 4 ++--
include/uapi/linux/pkt_cls.h | 6 +++---
net/sched/act_api.c| 19 +++
On 16-06-04 03:55 PM, Eric Dumazet wrote:
From: Eric Dumazet
My prior attempt to fix the backlogs of parents failed.
If we return NET_XMIT_CN, our parents wont increase their backlog,
so our qdisc_tree_reduce_backlog() should take this into account.
v2: Florian Westphal
From: Jamal Hadi Salim
Various aggregations of duplicated code, fixes and introduction of firstused
timestamp
Jamal Hadi Salim (3):
net sched: actions use tcf_lastuse_update for consistency
net sched actions: introduce timestamp for firsttime use
net sched actions:
From: Jamal Hadi Salim
Signed-off-by: Jamal Hadi Salim
---
net/sched/act_connmark.c | 2 +-
net/sched/act_csum.c | 2 +-
net/sched/act_ife.c | 6 +++---
net/sched/act_ipt.c | 2 +-
net/sched/act_mirred.c | 1 -
net/sched/act_nat.c | 2
Steven Rostedt suggests in reference to "[PATCH][RT] netpoll: Always
take poll_lock when doing polling"
>> [ Alison, can you try this patch ]
Sebastian follows up:
>Alison, did you try it?
Sorry for not responding sooner. I was hoping to come to a complete
understanding of the system before
It is my pleasure to announce to you the vacancy of a collection
representative post for China Textiles Ltd in your country,if you are
interested you will be given 5% for every collection made on our
clients, for more details
Respond.
Sincerely,
Dave Desmond.
On Sat, Jun 4, 2016 at 12:55 PM, Eric Dumazet wrote:
> From: Eric Dumazet
>
> My prior attempt to fix the backlogs of parents failed.
>
> If we return NET_XMIT_CN, our parents wont increase their backlog,
> so our qdisc_tree_reduce_backlog() should
Pablo Neira Ayuso writes:
> From: Florian Westphal
>
> We have targets and standard targets -- the latter carries a verdict.
>
> The ip/ip6tables validation functions will access t->verdict for the
> standard targets to fetch the jump offset or verdict for
The TX ring setup has an off by one error causing it to not utilise all
descriptors. This has the side effect that we need to reset the next
pointer at runtime to make it work. Fix the off by one and remove the
code fixing the ring at runtime.
Signed-off-by: John Crispin
---
The current code unconditionally wakes up the queue at the end of each
tx_poll action. Change the code to only wake up the queues if any of
them have actually been stopped before.
Signed-off-by: John Crispin
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 17
Commit 99aded71b52cfdfa22721c42e42efdd13a02f0a6 ("Staging: drivers: rtl8188eu:
use sizeof(*ptr) instead of sizeof(struct)") introduces an error in that the
sizeof(struct hal_data_8188e) is 18712, while the sizeof(*adapt->HalData) is
only 1! As a result, the system panics.
Fixes:
On Sun, 2016-06-05 at 13:30 -0700, Cong Wang wrote:
> On Sat, Jun 4, 2016 at 12:55 PM, Eric Dumazet wrote:
> > From: Eric Dumazet
> >
> > My prior attempt to fix the backlogs of parents failed.
> >
> > If we return NET_XMIT_CN, our parents wont
On Sun, 2016-06-05 at 13:54 -0700, Eric Dumazet wrote:
> BTW, we might need a similar fix in sch_fq.c
I meant sch_sfq.c
> > > > > Currently ethtool implementation does not have a way to pass the
> > > > > metadata for eeprom related operations. Some adapters have a
> > > > > complicated non-volatile memory implementation that requires
> > > > > additional information – there are drivers [bnx2x and bnxt] that
> > >
Commit fadbe0cd5292851608e2e01b91d9295fa287b9fe ("staging: rtl8188eu:
Remove rtw_zmalloc(), wrapper for kzalloc()") changed all allocation
calls to be GFP_KERNEL even though the original wrapper was testing
to determine if the caller was in atomic mode. Most of the mistakes
were corrected with
On 06/05/2016 02:53 PM, Sergei Shtylyov wrote:
On 6/4/2016 7:24 PM, Daniel Borkmann wrote:
[...]
Need a comment here, something like /* FALL THRU */.
Hmm, not really, I think it's obvious enough.
+default:
return -ENOENT;
-prio = TC_H_MAKE(0x8000U,
On Sun, Jun 5, 2016 at 2:14 AM, wrote:
> From: Zhu Yanjun
>
>
> Signed-off-by: Zhu Yanjun
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Sun, 2016-06-05 at 13:29 +, Yuval Mintz wrote:
> >
> > > > Currently ethtool implementation does not have a way to pass the
> > > > metadata for eeprom related operations. Some adapters have a
> > > > complicated non-volatile memory implementation that requires
> > > > additional
On Saturday 04 June 2016 08:07 PM, Kalle Valo wrote:
(Fixing top posting)
"Pan, Miaoqing" writes:
--- a/drivers/net/wireless/ath/ath9k/reg.h
+++ b/drivers/net/wireless/ath/ath9k/reg.h
@@ -1122,8 +1122,8 @@ enum {
#define AR9300_NUM_GPIO
Andreas Schwab wrote:
> > From: Florian Westphal
> >
> > We have targets and standard targets -- the latter carries a verdict.
> >
> > The ip/ip6tables validation functions will access t->verdict for the
> > standard targets to fetch the jump offset or
Le 04/06/2016 13:38, Andrew Lunn a écrit :
>> index e8386157de30..938262010524 100644
>> --- a/net/dsa/dsa2.c
>> +++ b/net/dsa/dsa2.c
>> @@ -346,7 +346,7 @@ static int dsa_ds_apply(struct dsa_switch_tree *dst,
>> struct dsa_switch *ds)
>> continue;
>> }
>>
>> -
Le 04/06/2016 13:00, Andrew Lunn a écrit :
>> -static int dsa_cpu_parse(struct device_node *port, u32 index,
>> - struct dsa_switch_tree *dst,
>> - struct dsa_switch *ds)
>> +static int _dsa_cpu_parse(struct dsa_switch_tree *dst,
>> +
On 03/06/16 10:56, LABBE Corentin wrote:
Hi,
first: thanks for posting this and the time and work that you spent on
it. With the respective DT nodes this works for me on the Pine64 and
turns this board eventually into something useful.
Some comments below:
> This patch add support for
On Sun, Jun 5, 2016 at 1:55 PM, Eric Dumazet wrote:
> On Sun, 2016-06-05 at 13:54 -0700, Eric Dumazet wrote:
>
>> BTW, we might need a similar fix in sch_fq.c
>
> I meant sch_sfq.c
>
Potentially all of the following:
net/sched/sch_choke.c: return NET_XMIT_CN;
This adds support for the Intel (former Lantiq) XWAY 11G and 22E PHYs.
These PHYs are also named PEF 7061, PEF 7071, PEF 7072.
Signed-off-by: John Crispin
Signed-off-by: Hauke Mehrtens
---
changes since last RFC:
* activated interrupts for all versions, if
This is now spitted out of the patch series that adds support the
Ethernet PHY. The second patch depends on the Ethernet PHY code which I
send before. How should this get merged, or should I split this in a
different way?
Hauke Mehrtens (2):
NET: PHY: Add PHY LED control binding.
NET: PHY:
This makes it possible to configure the behavior of the LEDs connected
to a PHY. The LEDs are controlled by the chip, this makes it possible
to configure the behavior when the hardware should activate and
deactivate the LEDs.
Signed-off-by: Hauke Mehrtens
---
This binding makes it possible to control the LEDs of an Ethernet PHY.
These settings allow it to abstract the hardware configuration which
tells the hardware when to switch the LED constant on or blink for
example. This will be used by the Intel XWAY PHY driver. I also
checked datasheets for
Le 04/06/2016 13:55, Andrew Lunn a écrit :
>> -static struct dsa_switch_driver bcm_sf2_switch_driver = {
>> +static struct dsa_switch_driver bcm_sf2_switch_ops = {
>> .tag_protocol = DSA_TAG_PROTO_BRCM,
>> .probe = bcm_sf2_sw_drv_probe,
>> .setup
Le 04/06/2016 13:29, Andrew Lunn a écrit :
>> @@ -517,6 +541,15 @@ static int dsa_parse_ports_dn(struct device_node
>> *ports, struct dsa_switch *ds)
>> return -EINVAL;
>>
>> ds->ports[reg].dn = port;
>> +
>> +if (dsa_port_is_cpu(port))
>> +
From: Colin King Sent: Sunday, June 05, 2016 3:01 AM
> To: Fugang Duan ; netdev@vger.kernel.org
> Cc: linux-ker...@vger.kernel.org
> Subject: [PATCH] net: fec: fix spelling mistake "coalesed" -> "coalesced"
>
> From: Colin Ian King
ay-ci/linux/commits/Zi-Shen-Lim/arm64-bpf-implement-bpf_tail_call-helper/20160605-060435
>> config: arm64-defconfig (attached as .config)
>> compiler: aarch64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
>> reproduce:
>> wget
>> https://git.kernel.org/cgi
On Sun, Jun 5, 2016 at 7:26 AM, Jamal Hadi Salim wrote:
> diff --git a/include/net/act_api.h b/include/net/act_api.h
> index 8389c00..5453f52 100644
> --- a/include/net/act_api.h
> +++ b/include/net/act_api.h
> @@ -80,6 +80,14 @@ static inline void tcf_lastuse_update(struct
On Fri, Jun 3, 2016 at 4:28 PM, David Miller wrote:
> From: Cong Wang
> Date: Wed, 1 Jun 2016 16:15:20 -0700
>
>> The police action is using its own code to initialize tcf hash
>> info, which makes us to forgot to initialize a->hinfo correctly.
>>
From: Michal Kubecek
Date: Fri, 27 May 2016 17:53:52 +0200
> Before commit 6d7b857d541e ("net: use lib/percpu_counter API for
> fragmentation mem accounting"), setting the reassembly high threshold
> to 0 prevented fragment reassembly as first fragment would be always
> evicted
From:
Date: Fri, 3 Jun 2016 02:07:15 -0700
> From: Tien Hock Loh
>
> This adds support for TSE PCS that uses SGMII adapter when the phy-mode of
> the dwmac is set to sgmii
>
> Signed-off-by: Tien Hock Loh
Please at least make an effort
From: Michal Schmidt
Date: Fri, 3 Jun 2016 15:32:18 +0200
> Since implementing VLAN filtering in commit 05cc5a39ddb74
> ("bnx2x: add vlan filtering offload") bnx2x refuses to add a VLAN while
> the interface is down:
>
> # ip link add link enp3s0f0 enp3s0f0_10 type vlan
From: Xin Long
Date: Fri, 3 Jun 2016 22:42:45 +0800
> Now sctp doesn't change socket state upon shutdown reception. It changes
> just the assoc state, even though it's a TCP-style socket.
>
> For some cases, if we really need to check sk->sk_state, it's necessary to
> fix
> How much support do we want to have for the old binding for in tree
> platforms? Is the plan to migrate them all to the new binding?
I think there are three cases to consider.
1) There are some old boards using setup.c files which have a platform
device, platform data, etc. I've never used
From: Vitaly Kuznetsov
Date: Fri, 3 Jun 2016 17:50:57 +0200
> Changes since v1:
> - resend when net-next is open [David Miller]
> - rebased to current net-next.
>
> After we made traveling through our internal structures explicit it became
> obvious that some functions
From: Andrew Lunn
Date: Fri, 3 Jun 2016 18:32:47 +0200
>> Reason for resend:
>> -Rebased on v4.7-rc1
>
> How do you see this getting merged? Via netdev? If so, you should be
> based on net-next/master, not v4.7-rc1.
Indeed, please respin.
Also, in your Subject lines, always
On Sat, Jun 04, 2016 at 09:35:27AM +0200, Phil Sutter wrote:
> [Cc'ing other interested parties, therefore full-quoting.]
>
> Hi Helge,
>
> On Fri, Jun 03, 2016 at 10:22:26PM +0200, Helge Deller wrote:
> > Hi Phil,
> >
> > I'm testing 4.7.0-rc1-64bit on a parisc/hppa machine and get
> > those
The code fails to check if the scratch memory was properly allocated. Add
this check and return with an error if the allocation failed.
Signed-off-by: John Crispin
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c |3 +++
1 file changed, 3 insertions(+)
diff --git
The MTK ethernet core has 2 MACs both sitting on the same DMA ring. For
DQL to be deterministic it needs to track the amount of data in the DMA
ring and not the amount of data enqueued on each device. The current code
is incorrect, fix it by making it each device track its own traffic aswell
as
If a future VF would send the PF an unknown message, the PF today would
not send a reply. This would have 2 bad effects:
a. VF would have to timeout on the request.
b. If VF were to send an additional message to PF, firmware would mark
it as malicious.
Instead, if there's some valid
The only limitation relating to MACs the PF enforce today on its VFs
is in case it has a forced-unicast MAC address for them, in which case
they can't configure other unicast addresses.
Specifically, the PF isn't enforcing the number of MAC addresse a VF can
configure regardless of the nubmer of
There are several requests the VF can make toward the PF which the driver
would pass to firmware without checking the validity first - specifically,
opening queues and updating vports. Such configurations might cause the
firmware to assert.
This adds validation of the legality of said
On Mon, Jun 6, 2016 at 6:32 AM, André Przywara wrote:
> On 03/06/16 10:56, LABBE Corentin wrote:
>
> Hi,
>
> first: thanks for posting this and the time and work that you spent on
> it. With the respective DT nodes this works for me on the Pine64 and
> turns this board
Got it, thanks. There is no difference of the changes for AR9462 which is the
chip Sudip tested.
Thanks,
Miaoqing
-Original Message-
From: Kalle Valo [mailto:kv...@codeaurora.org]
Sent: Saturday, June 04, 2016 10:38 PM
To: Pan, Miaoqing
Cc: Sudip Mukherjee
From: Lucas Stach Sent: Saturday, June 04, 2016 12:31
AM
> To: Shawn Guo ; Fugang Duan
> Cc: devicet...@vger.kernel.org; patchwork-...@pengutronix.de;
> ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
>
On Sun, Jun 05, 2016 at 03:29:01PM -0700, Florian Fainelli wrote:
> Le 04/06/2016 13:38, Andrew Lunn a écrit :
> >> index e8386157de30..938262010524 100644
> >> --- a/net/dsa/dsa2.c
> >> +++ b/net/dsa/dsa2.c
> >> @@ -346,7 +346,7 @@ static int dsa_ds_apply(struct dsa_switch_tree *dst,
> >> struct
On 2016年06月03日 21:04, Michael S. Tsirkin wrote:
On Fri, Jun 03, 2016 at 02:58:39PM +0200, Jesper Dangaard Brouer wrote:
>
>On Thu, 2 Jun 2016 19:08:26 +0300 "Michael S. Tsirkin" wrote:
>
> >A simple array based FIFO of pointers. Intended for net stack so uses
> >skbs for
91 matches
Mail list logo