linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: ubifs tree build failure
Date: Wed, 13 Aug 2008 12:58:06 +0300	[thread overview]
Message-ID: <48A2B02E.8020601@nokia.com> (raw)
In-Reply-To: <20080812213933.GA25538@lst.de>

Christoph Hellwig wrote:
> Btw, a good example for export ops on a filesystem with similar
> constraints is Dave's patch for jffs2:
> 
> 	http://git.kernel.org/?p=linux/kernel/git/viro/vfs-2.6.git;a=commitdiff;h=dd9207c31d6712a4665f197db7740da6c633cea7

OK, it is probably best if UBIFS NFS support goes via VFS git tree
just like JFFS2. I'll send a patch to fsdevel later.

Thus,  I'll remove NFS support from my tree and the conflict will
be solved.

Thanks.

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

  parent reply	other threads:[~2008-08-13  9:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  6:24 linux-next: ubifs tree build failure Stephen Rothwell
2008-08-12  7:11 ` Artem Bityutskiy
2008-08-12  7:37 ` Artem Bityutskiy
2008-08-12  8:42   ` Stephen Rothwell
2008-08-12 18:24   ` Christoph Hellwig
2008-08-13  9:42     ` Artem Bityutskiy
2008-08-12 18:24 ` Christoph Hellwig
2008-08-12 21:39   ` Christoph Hellwig
2008-08-13  6:23     ` Artem Bityutskiy
2008-08-13  9:58     ` Artem Bityutskiy [this message]
2008-08-13 11:20       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-11-24  1:14 Stephen Rothwell
2009-11-24  6:31 ` Artem Bityutskiy
2009-11-24  7:28   ` Stephen Rothwell

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=48A2B02E.8020601@nokia.com \
    --to=artem.bityutskiy@nokia.com \
    --cc=hch@lst.de \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).