From: Kees Cook <keescook@chromium.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v1 0/5] treewide cleanup of random integer usage
Date: Wed, 5 Oct 2022 23:15:31 -0700 [thread overview]
Message-ID: <202210052310.BF756EBEBE@keescook> (raw)
In-Reply-To: <20221005214844.2699-1-Jason@zx2c4.com>
On Wed, Oct 05, 2022 at 11:48:39PM +0200, Jason A. Donenfeld wrote:
> I've CC'd get_maintainers.pl, which is a pretty big list. Probably some
> portion of those are going to bounce, too, and everytime you reply to
The real problem is that replies may not reach the vger lists:
Subject: BOUNCE linux-kernel@vger.kernel.org: Header field too long (>8192)
But the originals somehow ended up on lore?
https://lore.kernel.org/lkml/20221005214844.2699-1-Jason@zx2c4.com/
--
Kees Cook
next parent reply other threads:[~2022-10-06 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221005214844.2699-1-Jason@zx2c4.com>
2022-10-06 6:15 ` Kees Cook [this message]
2022-10-06 12:58 ` [PATCH v1 0/5] treewide cleanup of random integer usage Jason A. Donenfeld
2022-10-06 8:17 ` Yann Droneaud
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=202210052310.BF756EBEBE@keescook \
--to=keescook@chromium.org \
--cc=Jason@zx2c4.com \
--cc=linux-api@vger.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;
as well as URLs for NNTP newsgroup(s).