Re: [Qemu-devel] using fdt_setprop() to set properties to empty values

[David Gibson <david@gibson.dropbear.id.au>]

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

On Fri, Feb 24, 2017 at 10:35:35AM +0000, Peter Maydell wrote:
> On 24 February 2017 at 00:16, David Gibson <david@gibson.dropbear.id.au> wrote:
> > Ok, I've pushed libfdt upstream patches to (a) make passing NULL to
> > setprop() with zero length explicitly safe and (b) add an
> > fdt_setprop_empty() helper macro.  Do you want me to make a pullreq to
> > update the qemu submodule?
> 
> Yes, please. Are we OK with using a random libfdt commit or do
> we update only to proper release tags?

I'm find with a random SHA, but that's not really my department - I'm
upstream libfdt maintainer, but update policy in the qemu tree seems
like a qemu side decision.

> There's no real rush with
> this so if you have a release due shortly it might be better
> to wait for that.

dtc/libfdt releases are a rather haphazard affair.  Usually they
happen when somebody complains that there hasn't been a release with
some feature they want.  Our tests are both fast to run and have
reasonaably good coverage, so random commits are usually good.  So a
"release" is usually just slapping a new version number onto whatever
is in master and making a tag and tarball.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]