From: Artem Bityutskiy <dedekind1@gmail.com>
To: Subodh Nijsure <snijsure@grid-net.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs_jnl_update and extended attribute inode removal
Date: Tue, 05 Jun 2012 15:07:07 +0300 [thread overview]
Message-ID: <1338898027.2507.46.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FAC4DC9.2050901@grid-net.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
On Thu, 2012-05-10 at 16:22 -0700, Subodh Nijsure wrote:
> > Would you prepare a description how I could reproduce this?
> I re-submitted patches for integck and as well as v3 of extended
> attribute patch set that I have been holding on to.
Hi, did I miss some patches from you or you just disappeared?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-05 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 3:19 ubifs_jnl_update and extended attribute inode removal Subodh Nijsure
2012-05-10 4:31 ` Artem Bityutskiy
2012-05-10 23:22 ` Subodh Nijsure
2012-06-05 12:07 ` Artem Bityutskiy [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=1338898027.2507.46.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=snijsure@grid-net.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).