From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH v6 02/12] Driver core: Unified device properties interface for platform firmware Date: Tue, 04 Nov 2014 22:29:08 +0100 Message-ID: <3275773.HN9MNfIOOq@vostro.rjw.lan> References: <13750506.S2yVlRRDa2@vostro.rjw.lan> <3645687.BsyGDrJDrU@vostro.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Grant Likely Cc: Linux Kernel Mailing List , Arnd Bergmann , ACPI Devel Maling List , Greg Kroah-Hartman , Darren Hart , Mika Westerberg , Aaron Lu , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Linus Walleij , Alexandre Courbot , Dmitry Torokhov , Bryan Wu List-Id: linux-acpi@vger.kernel.org On Tuesday, November 04, 2014 05:01:04 PM Grant Likely wrote: > On Mon, Nov 3, 2014 at 10:04 PM, Rafael J. Wysocki wrote: > >> I also found that this parser code doesn't correctly handle malformed > >> (unterminated) string properties. It will overflow. The existing > >> functions have the same problem, so it isn't something that you've > >> added. I've got a fix, and as a side effect the fix creates the _array > >> version basically for free as part of reworking > >> of_property_count_strings() and of_property_read_string_index() > > > > OK > > > > So can you please point me to a git branch containing the fix? I'll rebase the > > patch on top of that then and everything should merge just fine. > > git://git.kernel.org/pub/scm/linux/kernel/git/glikely/linux.git devicetree/merge > > I'm going to let the patch sit in there for a few days to get > linux-next exposure before I ask Linus to pull. The pull req will go > out before the end of the week. OK, thanks! Pulled, rebased my device-properties branch, merged into linux-pm.git/linux-next and pushed back. Rafael -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html