[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230213134811.elcgnzfryyxxegau@skbuf>
Date: Mon, 13 Feb 2023 15:48:11 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Richard van Schagen <richard@...terhints.com>
Cc: Sean Wang <sean.wang@...iatek.com>,
Landen Chao <Landen.Chao@...iatek.com>,
DENG Qingfang <dqfext@...il.com>, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Arinc Unal <arinc.unal@...nc9.com>,
Frank Wunderlich <frank-w@...lic-files.de>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] Fix Flooding: Disable by default on User ports and
Enable on CPU ports
NACK.
- the change needs to be localized to the file it touches by specifying the
"net: dsa: mt7530: " prefix.
- the rest of the 80-character short commit message needs to be a well
summarized description of the change.
- any time the "fix", "broken", etc words are used, a description of the
breakage is expected, and its projected impact upon users of the driver
- patches which solve a bug must have a Fixes: tag pointing to the patch
that introduced the problem
- if that patch being fixed is in the mainline kernel already, the
--subject-prefix of the patch must be "PATCH net", otherwise "PATCH
net-next". These correspond to the net.git and net-next.git trees.
- your signed-off tag is missing
- maybe more problems
Powered by blists - more mailing lists