From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: s3c2440: fix boot failure introduced by recent changes in gpiolib
Date: Wed, 08 Sep 2010 00:31:20 +0100 [thread overview]
Message-ID: <4C86CB48.6000502@fluff.org> (raw)
In-Reply-To: <1283537894-7463-1-git-send-email-awg@embtoolkit.org>
On 03/09/10 19:18, Abdoulaye Walsimou Gaye wrote:
> Recent changes in s3c gpio break mini2440 board and may be others.
> The problem is that mach-mini2440.c: mini2440_init()
> (where we call s3c_gpio_setpull()) is called before s3c2440.c: s3c2440_init()
> (where we initialize s3c24xx_gpiocfg_default.set_pull function pointer).
> This causes dereferencing of NULL pointer at boot time and a kernel panic.
>
> Signed-off-by: Abdoulaye Walsimou Gaye <awg@embtoolkit.org>
ok, i'll think over this. it is probably the right thing to do.
prev parent reply other threads:[~2010-09-07 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 18:18 [PATCH RESEND] ARM: s3c2440: fix boot failure introduced by recent changes in gpiolib Abdoulaye Walsimou Gaye
2010-09-07 23:31 ` Ben Dooks [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=4C86CB48.6000502@fluff.org \
--to=ben-linux@fluff.org \
--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).