From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mitchel Humpherys <mitchelh@codeaurora.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] coccinelle: Check for missing NULL terminators in of_device_id tables
Date: Tue, 27 May 2014 10:44:36 -0700 [thread overview]
Message-ID: <5384CF04.8080106@codeaurora.org> (raw)
In-Reply-To: <CAL_JsqJyCzNV0xK_uPp4o4F1Jhi8QmTY3KaHfeLcssnTea5H+Q@mail.gmail.com>
On 05/25/14 07:13, Rob Herring wrote:
> On Fri, May 23, 2014 at 6:41 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> Failure to terminate an of_device_id table can lead to confusing
>> failures depending on where the compiler places the array. Add a
>> check to make sure these tables are terminated. Thanks to Mitchel
>> Humpherys for coming up with the initial pattern.
> I've definitely debugged one of those problems. Do you have any actual
> fixes or there are no errors in the kernel?
>
>
Yes I sent five patches out. Here's one for example
https://lkml.org/lkml/2014/5/23/731
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2014-05-27 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 23:41 [PATCH] coccinelle: Check for missing NULL terminators in of_device_id tables Stephen Boyd
[not found] ` <1400888504-31309-1-git-send-email-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-05-24 7:57 ` Julia Lawall
2014-05-24 7:57 ` Julia Lawall
[not found] ` <alpine.DEB.2.02.1405240956220.2012-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2014-05-27 18:02 ` Stephen Boyd
2014-05-27 18:02 ` Stephen Boyd
2014-05-25 14:13 ` Rob Herring
2014-05-27 17:44 ` Stephen Boyd [this message]
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=5384CF04.8080106@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitchelh@codeaurora.org \
--cc=mmarek@suse.cz \
--cc=nicolas.palix@imag.fr \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.