From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] devdraw memory corruption
Date: Tue, 14 Jan 2014 00:54:47 +0100 [thread overview]
Message-ID: <34c05421e4e8c5f41ce637979bbaed82@felloff.net> (raw)
In-Reply-To: <2e748c14611ecd8e653a1865598e418d@felloff.net>
just saw, sources seems to have already fixed this
by using snprint()...
so never mind :)
--
cinap
next prev parent reply other threads:[~2014-01-13 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 23:44 cinap_lenrek
2014-01-13 23:54 ` cinap_lenrek [this message]
2014-01-13 23:54 ` erik quanstrom
2014-01-14 9:43 ` dexen deVries
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=34c05421e4e8c5f41ce637979bbaed82@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/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).