From: Robert Jarzmik <robert.jarzmik@free.fr>
To: barebox@lists.infradead.org
Subject: Re: Ramfs and NULL pointer
Date: Sun, 04 Nov 2012 19:48:07 +0100 [thread overview]
Message-ID: <87vcdlurvc.fsf@free.fr> (raw)
In-Reply-To: <87zk2xuuds.fsf@free.fr> (Robert Jarzmik's message of "Sun, 04 Nov 2012 18:53:51 +0100")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Hi there,
>
> Lately, I see null pointer dereferences in barebox.
> I traced the culprit to ramfs ...
Ah and if I take back v2012.09.0, the problem disappears.
I'm not fully in the mood for a bisection of 544 commits ... any idea ?
--
Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-11-04 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 17:53 Robert Jarzmik
2012-11-04 18:48 ` Robert Jarzmik [this message]
2012-11-04 22:56 ` Sascha Hauer
2012-11-05 8:23 ` Robert Jarzmik
2012-11-20 20:43 ` Robert Jarzmik
2012-11-20 20:50 ` Robert Jarzmik
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=87vcdlurvc.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=barebox@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