From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: Pinctrl crash on latest linux-next/master
Date: Tue, 17 Apr 2012 13:59:48 +0530 [thread overview]
Message-ID: <4F8D29FC.2010906@st.com> (raw)
In-Reply-To: <20120416140543.GC17173@shlinux2.ap.freescale.net>
On 4/16/2012 7:35 PM, Dong Aisheng wrote:
>>> > > I don't know if the issue is in my patches or something else, but i was
>>> > > able to boot it earlier. Till my V3 for pinctrl. And nothing much changed
>>> > > since then, i just rebased on latest kernel.
>> >
>> > Hm I haven't tested the pinctrl tree on v3.4-rc3 yet.
>> >
> Your for-next tree is ok since i'm working on it for pinctrl-imx driver. :-)
> It seems it's based on v3.4-rc2.
At last, found it. It was my code :(
I was writing on more memory than was allocated to me.
Thanks for your inputs.
--
viresh
prev parent reply other threads:[~2012-04-17 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:53 Pinctrl crash on latest linux-next/master Viresh Kumar
2012-04-16 12:50 ` Linus Walleij
2012-04-16 13:44 ` viresh kumar
2012-04-16 14:05 ` Dong Aisheng
2012-04-17 8:29 ` Viresh Kumar [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=4F8D29FC.2010906@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.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).