[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230213134157.k5ty4kko7xjhuvpt@skbuf>
Date: Mon, 13 Feb 2023 15:41:57 +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] Do not add all User ports to the CPU by default. This
will break Multi CPU when added a seperate patch. It will be overwritten by
.port_enable and since we are forcing output to a port via the Special Tag
this is not needed.
Hi Richard,
If Documentation/process/submitting-patches.rst does not completely
clarify, I also recommend running the "git log" command and studying
some of the formatting differences between this patch and any of the
patches that have been accepted.
Powered by blists - more mailing lists