From: Tim Sander <tim01@iss.tu-darmstadt.de>
To: linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: ubiformat & linux 3.0.14-rt
Date: Mon, 16 Jan 2012 11:43:22 +0100 [thread overview]
Message-ID: <201201161143.23934.tim01@iss.tu-darmstadt.de> (raw)
In-Reply-To: <1326468894.19039.45.camel@sauron.fi.intel.com>
Hi Artem
Thanks for your reply.
Am Freitag, 13. Januar 2012 schrieb Artem Bityutskiy:
> On Fri, 2012-01-13 at 10:06 +0100, Tim Sander wrote:
> > This happens with or without of ubifs master for 3.0 applied from
> > git://git.infradead.org/~dedekind/ubifs-v3.0.git
> >
> > So is there some condition which causes UBI(FS) to take more time in an
> > interrupt routine if the filesystem has been updated? If yes wouldn't it
> > be possible to move this work into:
> > ubifs_bgt0_0
>
> Please the very latest patches:
Mh, i'd like to. But this is with the realtime patches and i have only got 3.0
up and running. To my knowledge this error is only visible with the preempt rt
patch applied. So there are way to many merge conflicts for me to test :-(
sorry. I probably could give it a spin with 3.2-rt but i havent got this one
booting.
> http://git.infradead.org/ubifs-2.6.git
>
> Namely, these should fix the issue:
>
> http://git.infradead.org/ubifs-2.6.git/commit/1f5d78dc4823a85f112aaa2d0f176
> 24f8c2a6c52
> http://git.infradead.org/ubifs-2.6.git/commit/d34315da9146253351146140ea4b
> 277193ee5e5f
Do you think it is worthwhile checking the ubifs 3.0 backport with the above
two cherry-picked?
Best regards
Tim
next prev parent reply other threads:[~2012-01-16 10:43 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 [this message]
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
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=201201161143.23934.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