From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: st33zp24_i2c_send()
Date: Wed, 24 May 2017 14:14:50 -0700 [thread overview]
Message-ID: <20170524211450.q56ax2x5zs2p3zmp@intel.com> (raw)
In-Reply-To: <20170524205416.6nszazfyx454u5lm-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Wed, May 24, 2017 at 01:54:54PM -0700, Jarkko Sakkinen wrote:
> Hi
>
> When write8_reg() is called through st33zp24_send(), how it is ensured
> to memcpy() does not overflow?
~~
that
/Jarkko
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
parent reply other threads:[~2017-05-24 21:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170524205416.6nszazfyx454u5lm-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>]
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=20170524211450.q56ax2x5zs2p3zmp@intel.com \
--to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).