From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 21464136A for ; Tue, 13 Jun 2023 20:29:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A052CC433C8; Tue, 13 Jun 2023 20:29:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1686688176; bh=Mto+CBG6oIkTZvT58Ap2W7GNwLzNDVjVgeAmeD03zOg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Nzk1BR4xRN5+OzHBp4o2VQxT0E5D2cSXXYJG4QB5SlhJyEzpvqlKdKP046mmolxaO XmTmjkv2N5T1TGGt4QVgmxTV2V1tn9g4B6Y2FMQhvG1V9jjSTtxWZaDqSNgirV891/ NEGXortM1jHgFodE4xphi1cxfPBLfbUfPA4qb/zjgg749UKElaeaaQdQEeAZxMP6Y/ vxn1YTUS7MGDu3HxBYtPSs2/sOYGp49sSnyunNSqOoAZ91aYmPBBANTg5BYXnCkdUd wC7EshH/jYYAli5d2iE147VWjs6aHYm3ii9pRdxswSWUj2VP6EoaZy+HWFM8FShAg6 qSL74MTafHKvA== Date: Tue, 13 Jun 2023 13:29:34 -0700 From: Jakub Kicinski To: =?UTF-8?B?QXLEsW7DpyDDnE5BTA==?= Cc: Vladimir Oltean , Daniel Golle , Landen Chao , DENG Qingfang , Sean Wang , Andrew Lunn , Florian Fainelli , "David S. Miller" , Eric Dumazet , Paolo Abeni , Matthias Brugger , AngeloGioacchino Del Regno , Russell King , Frank Wunderlich , Bartel Eerdekens , mithat.guner@xeront.com, erkin.bozoglu@xeront.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH net v2 2/7] net: dsa: mt7530: fix trapping frames with multiple CPU ports on MT7530 Message-ID: <20230613132934.1da72c99@kernel.org> In-Reply-To: <1761c20e-5f94-cb21-6170-0c39520062d6@arinc9.com> References: <20230611081547.26747-1-arinc.unal@arinc9.com> <20230611081547.26747-2-arinc.unal@arinc9.com> <20230613150815.67uoz3cvvwgmhdp2@skbuf> <20230613171858.ybhtlwxqwp7gyrfs@skbuf> <20230613172402.grdpgago6in4jogq@skbuf> <20230613173908.iuofbuvkanwyr7as@skbuf> <20230613111218.0e1b3e9f@kernel.org> <359d0825-e39a-8a12-ebbf-b8d7e941d1ef@arinc9.com> <1761c20e-5f94-cb21-6170-0c39520062d6@arinc9.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, 13 Jun 2023 22:09:02 +0300 Ar=C4=B1n=C3=A7 =C3=9CNAL wrote: > >> It's a new capability that nobody has used, yet, so YMMV :) =20 > >=20 > > Interesting, I've got some questions regarding this. > > =20 > >> For example to mark a series as Changes Requested one needs to send=20 > >> the following line anywhere in the email thread: > >> > >> pw-bot: changes-requested =20 > >=20 > > I suppose a reply to the cover letter or under the cover letter thread= =20 > > applies? Anywhere in the thread, the bot should walk references. > >> The use of the bot is restricted to authors of the patches (the From:= =20 > >> header on patch submission and command must match!) =20 > >=20 > > So, for example, if this patch series was new, Vladimir would reply to= =20 > > the patch they're the author of with 'pw-bot: changes-requested', and=20 > > the patchworks would mark the whole patch series as changes requested? = =20 Yes. > Also, replying with 'pw-bot: changes-requested' on an already accepted=20 > patch series as the author won't change the state from accepted to=20 > changes requested, correct? Yes, authors can only changes status from active to inactive. Accepted is an inactive state.