On Mon, Apr 15, 2013 at 10:13:09PM -0400, Mike Frysinger wrote:
> For a follow up commit, we want to be able to scan the buffer that was
> returned to us. In order to do that safely, we need to know how big
> the buffer actually is, so create a new set of funcs to pass that back.
>
> Signed-off-b
For a follow up commit, we want to be able to scan the buffer that was
returned to us. In order to do that safely, we need to know how big
the buffer actually is, so create a new set of funcs to pass that back.
Signed-off-by: Mike Frysinger
---
util.c | 19 ---
util.h | 13 +
On Monday 15 April 2013 00:58:38 David Gibson wrote:
> On Wed, Apr 10, 2013 at 02:29:07PM -0400, Mike Frysinger wrote:
> > For a follow up commit, we want to be able to scan the buffer that was
> > returned to us. In order to do that safely, we need to know how big
> > the buffer actually is, so p
On Wed, Apr 10, 2013 at 02:29:07PM -0400, Mike Frysinger wrote:
> For a follow up commit, we want to be able to scan the buffer that was
> returned to us. In order to do that safely, we need to know how big
> the buffer actually is, so pass that back if requested.
Rather than changing all the cal
For a follow up commit, we want to be able to scan the buffer that was
returned to us. In order to do that safely, we need to know how big
the buffer actually is, so pass that back if requested.
Signed-off-by: Mike Frysinger
---
fdtget.c | 2 +-
fdtput.c | 2 +-
tests/testutil
