All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jeff Angielski <jeff@theptrgroup.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-mtd@lists.infradead.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Matt Mackall <mpm@selenic.com>
Subject: Re: UBIFS assert failed in ubifs_dirty_inode
Date: Tue, 02 Feb 2010 12:42:15 +0200	[thread overview]
Message-ID: <1265107335.4371.68.camel@localhost> (raw)
In-Reply-To: <4B5FADE8.30803@theptrgroup.com>

On Tue, 2010-01-26 at 22:07 -0500, Jeff Angielski wrote:
... snip ...
> Matt's patch that removes the offending code works fine.
... snip ...

Jeff, I've pushed the patches from Herbert's tree to the ubifs back-port
trees (ubifs-v2.6.28 - ubifs-v2.6.32).

Thanks everyone.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jeff Angielski <jeff@theptrgroup.com>
Cc: Matt Mackall <mpm@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-mtd@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: UBIFS assert failed in ubifs_dirty_inode
Date: Tue, 02 Feb 2010 12:42:15 +0200	[thread overview]
Message-ID: <1265107335.4371.68.camel@localhost> (raw)
In-Reply-To: <4B5FADE8.30803@theptrgroup.com>

On Tue, 2010-01-26 at 22:07 -0500, Jeff Angielski wrote:
... snip ...
> Matt's patch that removes the offending code works fine.
... snip ...

Jeff, I've pushed the patches from Herbert's tree to the ubifs back-port
trees (ubifs-v2.6.28 - ubifs-v2.6.32).

Thanks everyone.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)


  parent reply	other threads:[~2010-02-02 10:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  3:03 UBIFS assert failed in ubifs_dirty_inode Jeff Angielski
2010-01-24 21:07 ` Artem Bityutskiy
2010-01-25 21:03   ` Jeff Angielski
2010-01-26  4:40 ` Artem Bityutskiy
2010-01-26  4:40   ` Artem Bityutskiy
2010-01-26  5:48   ` Matt Mackall
2010-01-26 10:03     ` Artem Bityutskiy
2010-01-26 10:07       ` Artem Bityutskiy
2010-01-27  1:44       ` Jeff Angielski
2010-01-27  1:44         ` Jeff Angielski
2010-01-27  2:13         ` Matt Mackall
2010-01-27  2:13           ` Matt Mackall
2010-01-27  3:07           ` Jeff Angielski
2010-01-27  3:07             ` Jeff Angielski
2010-01-27  4:20             ` Artem Bityutskiy
2010-01-27  4:20               ` Artem Bityutskiy
2010-01-27  5:14               ` Matt Mackall
2010-01-27  5:14                 ` Matt Mackall
2010-01-29 11:27               ` Herbert Xu
2010-01-29 11:27                 ` Herbert Xu
2010-01-29 11:32                 ` Artem Bityutskiy
2010-01-29 11:32                   ` Artem Bityutskiy
2010-01-29 11:35                   ` Herbert Xu
2010-01-29 11:35                     ` Herbert Xu
2010-02-02 10:42             ` Artem Bityutskiy [this message]
2010-02-02 10:42               ` Artem Bityutskiy
2010-01-29  8:48     ` Herbert Xu
2010-01-29  8:48       ` Herbert Xu

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=1265107335.4371.68.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jeff@theptrgroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mpm@selenic.com \
    /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.