From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Bedel, Alban" <alban.bedel@aerq.com>
Cc: Claudiu Manoil <claudiu.manoil@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH] net: mscc: ocelot: Fix multicast to the CPU port
Date: Tue, 19 Jan 2021 10:51:23 +0000 [thread overview]
Message-ID: <20210119105123.b3emeo22ykwyrot7@skbuf> (raw)
In-Reply-To: <2cb97bec861c751530a04a9764b8855c8e8e2e41.camel@aerq.com>
On Tue, Jan 19, 2021 at 10:12:34AM +0000, Bedel, Alban wrote:
> My board use felix and I build without CONFIG_MSCC_OCELOT_SWITCH so I
> missed these, my bad.
Ah, ok, this makes sense. It happens to me too to forget to build with
CONFIG_MSCC_OCELOT_SWITCH enabled, more often than I'd like to admit.
> I must say that this condescending tone is a real turn off.
English is not my first language, it probably sounds harsher than it is
when translated ;)
So could you please resend a patch which:
- has a Fixes: tag with 12 characters in the sha1sum
- compiles with CONFIG_MSCC_OCELOT_SWITCH
- has a --subject-prefix of "PATCH v2 net"
- can be cherry-picked on linux-5.10.y and linux-5.9.y from
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/,
but also to the net tree, which is where the patch will first be
applied:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
prev parent reply other threads:[~2021-01-19 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 16:03 [PATCH] net: mscc: ocelot: Fix multicast to the CPU port Alban Bedel
2021-01-18 18:55 ` Vladimir Oltean
2021-01-19 10:12 ` Bedel, Alban
2021-01-19 10:51 ` Vladimir Oltean [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210119105123.b3emeo22ykwyrot7@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alban.bedel@aerq.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox