From: ihsinme <ihsinme@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: ihsinme <ihsinme@gmail.com>
Subject: [PATCH BlueZ 0/1] fix writing out of bounds array
Date: Tue, 1 Mar 2022 06:14:44 +0000 [thread overview]
Message-ID: <20220301061445.7626-1-ihsinme@gmail.com> (raw)
see https://github.com/bluez/bluez/pull/303
ihsinme (1):
fix writing out of bounds array
src/device.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.35.1
next reply other threads:[~2022-03-01 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 6:14 ihsinme [this message]
2022-03-01 6:14 ` [PATCH BlueZ 1/1] fix writing out of bounds array ihsinme
2022-03-01 7:36 ` bluez.test.bot
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=20220301061445.7626-1-ihsinme@gmail.com \
--to=ihsinme@gmail.com \
--cc=linux-bluetooth@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).