From: Casper Andersson <casper@casan.se>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: sparx5: Support offloading of bridge port flooding flags
Date: Fri, 18 Feb 2022 09:01:30 +0000 [thread overview]
Message-ID: <20220218090127.vutf5qomnobcof4z@wse-c0155> (raw)
In-Reply-To: <20220217201830.51419e5e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 22/02/17 08:18, Jakub Kicinski wrote:
> On Thu, 17 Feb 2022 14:45:38 +0000 Casper Andersson wrote:
>
> Can others see this patch? My email client apparently does not have
> enough PGP support enabled. I'm worried I'm not the only one. That said
> lore and patchwork seem to have gotten it just fine:
>
> https://lore.kernel.org/all/20220217144534.sqntzdjltzvxslqo@wse-c0155/
> https://patchwork.kernel.org/project/netdevbpf/patch/20220217144534.sqntzdjltzvxslqo@wse-c0155/
I apologize. This seems to be Protonmail's doing. When I look at the
web interface for Protonmail I can see that you are the only recipient
it says PGP encrypted for. This is probably because Protonmail will
automatically encrypt when both ends use Protonmail. Though I do not see
this indication on your reply. I tried switching to PGP/Inline instead
of PGP/MIME for this message. I hope this works. Otherwise, I can
resubmit this patch using another email address. I did not find a way
to disable the automatic encryption. Or if you have any other
suggestions to get around this.
next prev parent reply other threads:[~2022-02-18 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 14:45 [PATCH net-next] net: sparx5: Support offloading of bridge port flooding flags Casper Andersson
2022-02-18 4:18 ` Jakub Kicinski
2022-02-18 9:01 ` Casper Andersson [this message]
2022-02-19 4:26 ` Jakub Kicinski
2022-02-19 14:56 ` Horatiu Vultur
2022-02-22 18:30 ` Jakub Kicinski
2022-02-21 7:59 ` Steen Hegelund
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=20220218090127.vutf5qomnobcof4z@wse-c0155 \
--to=casper@casan.se \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--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;
as well as URLs for NNTP newsgroup(s).