From: Tim Sander <tim01@iss.tu-darmstadt.de>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiformat & linux 3.0.14-rt
Date: Wed, 18 Jan 2012 15:38:31 +0100 [thread overview]
Message-ID: <201201181538.33048.tim01@iss.tu-darmstadt.de> (raw)
In-Reply-To: <1326896252.28477.17.camel@sauron.fi.intel.com>
Hi Artem
I just found out that the error i attributed to ubifs is most likely within
the network code. Its just that after the ubiimage has been attached
the network was reconfigured. I first attributed it to the ubi code since this
always happened so close to the ubiattach and was related with firmware update.
Sorry for the noise and thanks for your support.
Tim
prev parent reply other threads:[~2012-01-18 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 9:06 ubiformat & linux 3.0.14-rt Tim Sander
2012-01-13 15:34 ` Artem Bityutskiy
2012-01-16 10:43 ` Tim Sander
2012-01-16 11:19 ` Artem Bityutskiy
2012-01-16 12:59 ` Tim Sander
2012-01-16 13:04 ` Artem Bityutskiy
2012-01-16 14:59 ` Tim Sander
2012-01-18 14:17 ` Artem Bityutskiy
2012-01-18 14:38 ` Tim Sander [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=201201181538.33048.tim01@iss.tu-darmstadt.de \
--to=tim01@iss.tu-darmstadt.de \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@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