From: Paolo Abeni <pabeni@redhat.com>
To: Carlos Fernandez <carlos.fernandez@technica-engineering.de>,
Carlos Fernandez <carlos.escuin@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"mayflowerera@gmail.com" <mayflowerera@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: macsec: Retrieve MACSec-XPN attributes before offloading
Date: Thu, 30 Jun 2022 12:00:30 +0200 [thread overview]
Message-ID: <9a3c3660f4e32be7d490e2abfe9bc364162ec74b.camel@redhat.com> (raw)
In-Reply-To: <AM9PR08MB67887876922C0E9842EAE88ADBBA9@AM9PR08MB6788.eurprd08.prod.outlook.com>
On Thu, 2022-06-30 at 08:51 +0000, Carlos Fernandez wrote:
> Sorry about that, I was pretty sure I added it in the first line of the patch and then I used git send-email.
> Is there any way that I can be sure everything is ok before sending it? I'll try again.
As a last resort thing, you can git send-email to another account under
your control (_only_ to that recipient!), git am <email> on a clean -
net tree and check that everything is fine.
Cheers,
Paolo
next prev parent reply other threads:[~2022-06-30 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 11:41 [PATCH net] net: macsec: Retrieve MACSec-XPN attributes before offloading Carlos Fernandez
2022-05-26 8:59 ` Paolo Abeni
2022-05-26 12:21 ` Carlos Fernandez
2022-06-28 11:16 ` Carlos Fernandez
2022-06-30 8:16 ` Paolo Abeni
2022-06-30 8:51 ` Carlos Fernandez
2022-06-30 10:00 ` Paolo Abeni [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-26 12:28 Carlos Fernandez
2022-05-28 1:37 ` Jakub Kicinski
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=9a3c3660f4e32be7d490e2abfe9bc364162ec74b.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=carlos.escuin@gmail.com \
--cc=carlos.fernandez@technica-engineering.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mayflowerera@gmail.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).