From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 00/18] net: dsa: mv88e6xxx: 802.1s and 88E6390 VTU Date: Mon, 01 May 2017 12:26:18 -0400 (EDT) Message-ID: <20170501.122618.1787371573631638101.davem@davemloft.net> References: <871ss8bmom.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me> <20170501.120800.1973590139715167836.davem@davemloft.net> <87shko7dkk.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com, f.fainelli@gmail.com, andrew@lunn.ch To: vivien.didelot@savoirfairelinux.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:34232 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751463AbdEAQ0U (ORCPT ); Mon, 1 May 2017 12:26:20 -0400 In-Reply-To: <87shko7dkk.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me> Sender: netdev-owner@vger.kernel.org List-ID: From: Vivien Didelot Date: Mon, 01 May 2017 12:21:31 -0400 > Hi David, > > David Miller writes: > >> From: Vivien Didelot >> Date: Mon, 01 May 2017 11:51:05 -0400 >> >>> Hi David, >>> >>> Vivien Didelot writes: >>> >>>> Vivien Didelot (18): >>>> net: dsa: mv88e6xxx: add max VID to info >>>> net: dsa: mv88e6xxx: split VTU entry data member >>>> net: dsa: mv88e6xxx: move VTU Operation accessors >>>> net: dsa: mv88e6xxx: move VTU flush >>>> net: dsa: mv88e6xxx: move VTU FID accessors >>>> net: dsa: mv88e6xxx: move VTU SID accessors >>>> net: dsa: mv88e6xxx: move VTU VID accessors >>>> net: dsa: mv88e6xxx: move generic VTU GetNext >>>> net: dsa: mv88e6xxx: move VTU Data accessors >>>> net: dsa: mv88e6xxx: move STU GetNext operation >>>> net: dsa: mv88e6xxx: get STU entry on VTU GetNext >>>> net: dsa: mv88e6xxx: load STU entry with VTU entry >>>> net: dsa: mv88e6xxx: add VTU GetNext operation >>>> net: dsa: mv88e6xxx: add VTU Load/Purge operation >>>> net: dsa: mv88e6xxx: make VTU helpers static >>>> net: dsa: mv88e6xxx: simplify VTU entry getter >>>> net: dsa: mv88e6xxx: support the VTU Page bit >>>> net: dsa: mv88e6xxx: add VTU support for 88E6390 >>>> >>>> drivers/net/dsa/mv88e6xxx/Makefile | 1 + >>>> drivers/net/dsa/mv88e6xxx/chip.c | 568 +++++++++----------------------- >>>> drivers/net/dsa/mv88e6xxx/global1.h | 14 + >>>> drivers/net/dsa/mv88e6xxx/global1_vtu.c | 505 ++++++++++++++++++++++++++++ >>>> drivers/net/dsa/mv88e6xxx/mv88e6xxx.h | 31 +- >>>> 5 files changed, 684 insertions(+), 435 deletions(-) >>>> create mode 100644 drivers/net/dsa/mv88e6xxx/global1_vtu.c >>> >>> I don't see the patchset in net-next. Can you pick it? >> >> This had feedback which you must address, therefore the state in >> patchwork is "changes requested" which you could have checked before >> asking me this. >> >> If the patch set is fine and you got ACKs for all of your patches >> then please resubmit. >> >> Otherwise, make the changes you were asked to make or explain to >> the person who asked for them why they are not appropriate. > > We did discuss the patchset and everything is good as is. Can someone > change the state in patchwork afterwards? It feels weird to resend the > patch with no changes. Once I set the state to "changes requested", that's basically permanent. Please simply resubmit your patch series, ACKs added if necessary. Thanks.