Re: [PATCH net 00/10] qed*: Bug fixes

2017-02-20 Thread David Miller 
From: "Mintz, Yuval" 
Date: Mon, 20 Feb 2017 20:14:17 +

>  > > Hi Dave,
>> >
>> > The 3 first patches here are a repost of
>> > ("qed: RoCE infrastructure fixes"). The fourth is an additional
>> > RoCE-related infrastructure fix, and the latter contain various fixes
>> > to qed/qede.
>> >
>> > Notice patch #10 will create a conflict when net and net-next would be
>> > merged [although its fix is quite trivial].
>> >
>> > Please consider applying these to `net'.
>> 
>> Linus made his release so all patches are going into net-next, which this
>> series doesn't apply cleanly to.  Please therefore respin your series against
>> net-next, thanks.
> 
> Just to clarify - do you want me to re-spin the fixes against next-next *now*,
> or do you want me to wait until it re-opens? [not sure on its exact state]

Yes, now.

RE: [PATCH net 00/10] qed*: Bug fixes

2017-02-20 Thread Mintz, Yuval 
 > > Hi Dave,
> >
> > The 3 first patches here are a repost of
> > ("qed: RoCE infrastructure fixes"). The fourth is an additional
> > RoCE-related infrastructure fix, and the latter contain various fixes
> > to qed/qede.
> >
> > Notice patch #10 will create a conflict when net and net-next would be
> > merged [although its fix is quite trivial].
> >
> > Please consider applying these to `net'.
> 
> Linus made his release so all patches are going into net-next, which this
> series doesn't apply cleanly to.  Please therefore respin your series against
> net-next, thanks.

Just to clarify - do you want me to re-spin the fixes against next-next *now*,
or do you want me to wait until it re-opens? [not sure on its exact state]

Re: [PATCH net 00/10] qed*: Bug fixes

2017-02-20 Thread David Miller 
From: Yuval Mintz 
Date: Sun, 19 Feb 2017 15:26:13 +0200

> Hi Dave,
> 
> The 3 first patches here are a repost of
> ("qed: RoCE infrastructure fixes"). The fourth is an additional
> RoCE-related infrastructure fix, and the latter contain various fixes
> to qed/qede.
> 
> Notice patch #10 will create a conflict when net and net-next would
> be merged [although its fix is quite trivial].
> 
> Please consider applying these to `net'.

Linus made his release so all patches are going into net-next, which
this series doesn't apply cleanly to.  Please therefore respin your
series against net-next, thanks.

[PATCH net 00/10] qed*: Bug fixes

2017-02-19 Thread Yuval Mintz 
Hi Dave,

The 3 first patches here are a repost of
("qed: RoCE infrastructure fixes"). The fourth is an additional
RoCE-related infrastructure fix, and the latter contain various fixes
to qed/qede.

Notice patch #10 will create a conflict when net and net-next would
be merged [although its fix is quite trivial].

Please consider applying these to `net'.

Thanks,
Yuval

Ram Amrani (4):
  qed: Release CQ resource under lock on failure
  qed: Read queue state before releasing buffer
  qed: Don't free a QP more than once
  qed: Reserve doorbell BAR space for all present CPUs

Sudarsana Reddy Kalluru (1):
  qede: Prevent index problems in loopback test

Yuval Mintz (5):
  qede: Initialize lock and slowpath workqueue early
  qede: Free netdevice only after stoping slowpath
  qed: Reflect PF link when initializing VF
  qed: Don't allocate SBs using main PTT
  qed*: Fix link indication race

 drivers/net/ethernet/qlogic/qed/qed_dev.c   |  2 +-
 drivers/net/ethernet/qlogic/qed/qed_main.c  | 27 ++--
 drivers/net/ethernet/qlogic/qed/qed_mcp.c   | 18 +++--
 drivers/net/ethernet/qlogic/qed/qed_mcp.h   |  6 ++
 drivers/net/ethernet/qlogic/qed/qed_roce.c  | 63 +
 drivers/net/ethernet/qlogic/qed/qed_sriov.c | 90 ++---
 drivers/net/ethernet/qlogic/qed/qed_sriov.h |  1 +
 drivers/net/ethernet/qlogic/qed/qed_vf.c|  3 +
 drivers/net/ethernet/qlogic/qede/qede_ethtool.c |  6 +-
 drivers/net/ethernet/qlogic/qede/qede_main.c| 24 ---
 10 files changed, 151 insertions(+), 89 deletions(-)

-- 
1.9.3