Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 13 Jun 2023 13:29:34 -0700
From:   Jakub Kicinski <kuba@kernel.org>
To:     =?UTF-8?B?QXLEsW7DpyDDnE5BTA==?= <arinc.unal@arinc9.com>
Cc:     Vladimir Oltean <olteanv@gmail.com>,
        Daniel Golle <daniel@makrotopia.org>,
        Landen Chao <Landen.Chao@mediatek.com>,
        DENG Qingfang <dqfext@gmail.com>,
        Sean Wang <sean.wang@mediatek.com>,
        Andrew Lunn <andrew@lunn.ch>,
        Florian Fainelli <f.fainelli@gmail.com>,
        "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Paolo Abeni <pabeni@redhat.com>,
        Matthias Brugger <matthias.bgg@gmail.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@collabora.com>,
        Russell King <linux@armlinux.org.uk>,
        Frank Wunderlich <frank-w@public-files.de>,
        Bartel Eerdekens <bartel.eerdekens@constell8.be>,
        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>
        <a91e88a8-c528-0392-1237-fc8417931170@arinc9.com>
        <20230613171858.ybhtlwxqwp7gyrfs@skbuf>
        <20230613172402.grdpgago6in4jogq@skbuf>
        <ca78b2f9-bf98-af26-0267-60d2638f7f00@arinc9.com>
        <20230613173908.iuofbuvkanwyr7as@skbuf>
        <edcbe326-c456-06ef-373b-313e780209de@arinc9.com>
        <20230613111218.0e1b3e9f@kernel.org>
        <359d0825-e39a-8a12-ebbf-b8d7e941d1ef@arinc9.com>
        <1761c20e-5f94-cb21-6170-0c39520062d6@arinc9.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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.