From: Greg KH <greg@kroah.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-rc4 jffs2 problems
Date: Sun, 20 Aug 2006 18:35:45 -0700 [thread overview]
Message-ID: <20060821013545.GA21012@kroah.com> (raw)
In-Reply-To: <625fc13d0608191834r19ce12e5raccbae011d67c25e@mail.gmail.com>
On Sat, Aug 19, 2006 at 08:34:46PM -0500, Josh Boyer wrote:
> On 8/17/06, Richard Purdie <rpurdie@rpsys.net> wrote:
> >Read the return value before we release the nand device otherwise the
> >value can become corrupted by another user of chip->ops, ultimately
> >resulting in filesystem corruption.
> >
>
> We have multiple confirmations that this patch fixes the issue
> reported. I agree it should go in 2.6.18.
>
> Greg, can you add this to your tree?
Add what to what tree? I need things to be a bit more specific here :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
linux-mtd <linux-mtd@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: 2.6.18-rc4 jffs2 problems
Date: Sun, 20 Aug 2006 18:35:45 -0700 [thread overview]
Message-ID: <20060821013545.GA21012@kroah.com> (raw)
In-Reply-To: <625fc13d0608191834r19ce12e5raccbae011d67c25e@mail.gmail.com>
On Sat, Aug 19, 2006 at 08:34:46PM -0500, Josh Boyer wrote:
> On 8/17/06, Richard Purdie <rpurdie@rpsys.net> wrote:
> >Read the return value before we release the nand device otherwise the
> >value can become corrupted by another user of chip->ops, ultimately
> >resulting in filesystem corruption.
> >
>
> We have multiple confirmations that this patch fixes the issue
> reported. I agree it should go in 2.6.18.
>
> Greg, can you add this to your tree?
Add what to what tree? I need things to be a bit more specific here :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-21 1:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 18:41 2.6.18-rc4 jffs2 problems Richard Purdie
2006-08-08 6:40 ` Andrew Morton
2006-08-08 7:15 ` Artem B. Bityutskiy
2006-08-09 9:34 ` Jonathan McDowell
2006-08-10 6:04 ` Jonathan McDowell
2006-08-10 9:29 ` Artem B. Bityutskiy
2006-08-15 22:29 ` Richard Purdie
2006-08-17 22:09 ` Richard Purdie
2006-08-20 1:34 ` Josh Boyer
2006-08-20 1:34 ` Josh Boyer
2006-08-21 1:35 ` Greg KH [this message]
2006-08-21 1:35 ` Greg KH
2006-08-22 14:12 ` David Woodhouse
2006-08-22 14:12 ` David Woodhouse
2006-08-22 14:39 ` Josh Boyer
2006-08-22 14:39 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 8:07 Koeller, T.
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=20060821013545.GA21012@kroah.com \
--to=greg@kroah.com \
--cc=dwmw2@infradead.org \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.