From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Hodges <hodgesd@meta.com>
Cc: netdev@vger.kernel.org, "<^[@fb.com>," <jmaloy@redhat.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, tuong.t.lien@dektech.com.au,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH 1/3] tipc: use kfree_sensitive() for session key material
Date: Sat, 31 Jan 2026 09:08:15 -0800 [thread overview]
Message-ID: <20260131090815.73ae7b09@kernel.org> (raw)
In-Reply-To: <aX15HnlN8B_JOpMC@fb.com>
On Fri, 30 Jan 2026 19:39:25 -0800 Daniel Hodges wrote:
> Whoops, this should only be one patch, I messed up when separating this
> patch out.
You'll need to resend, unfortunately, patchwork will wait for
the "other two patches" forever and never kick off our CI :(
next prev parent reply other threads:[~2026-01-31 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 3:25 [PATCH 1/3] tipc: use kfree_sensitive() for session key material Daniel Hodges
2026-01-31 3:39 ` Daniel Hodges
2026-01-31 17:08 ` Jakub Kicinski [this message]
2026-01-31 17:52 ` Daniel Hodges
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=20260131090815.73ae7b09@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hodgesd@meta.com \
--cc=horms@kernel.org \
--cc=jmaloy@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tuong.t.lien@dektech.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.