From: Colin Wee <cwee@tesla.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject:
Date: Fri, 10 May 2024 23:41:56 +0000 [thread overview]
Message-ID: <20240510234137.3619779-1-cwee@tesla.com> (raw)
In-Reply-To: <555F580E-1735-4CB1-89F0-7866013F6D47@holtmann.org>
Sure thing! I've updated the patch, let me know how else I can help.
-Colin
next prev parent reply other threads:[~2024-05-10 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 21:58 [PATCH] Prevent a short allocation by checking upper_length Colin Wee
2024-05-08 15:47 ` Marcel Holtmann
2024-05-10 23:41 ` Colin Wee [this message]
2024-05-10 23:51 ` Colin Wee
2024-05-10 23:53 ` Colin Wee
2024-05-10 23:53 ` [PATCH] Prevent a short allocation by checking upper_length Colin Wee
2024-05-24 21:30 ` Colin Wee
2024-05-28 15:45 ` Denis Kenzior
2024-05-28 16:08 ` patchwork-bot+connman
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=20240510234137.3619779-1-cwee@tesla.com \
--to=cwee@tesla.com \
--cc=connman@lists.linux.dev \
--cc=marcel@holtmann.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 read-only IMAP folder(s) and NNTP newsgroup(s).