All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Artem.Bityutskiy@nokia.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: can UBIFS be taken to linux-next?
Date: Tue, 27 May 2008 19:29:42 -0700	[thread overview]
Message-ID: <20080527192942.f4e3dd7b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080528114112.b8600074.sfr@canb.auug.org.au>

On Wed, 28 May 2008 11:41:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Artem,
> 
> On Tue, 27 May 2008 09:18:07 +0300 Artem Bityutskiy <Artem.Bityutskiy@nokia.com> wrote:
> >
> > we would like to ask for UBIFS mainline inclusion the next merge window.
> > Of course we cannot say for sure whether Linus will merge it or not,
> > but it would be helpful to have it in your tree for some time anyway.
> > UBIFS is already in -mm tree so I assume it should not have too many
> > build issues.
> 
> OK, my requirements are that you intend for it to be integrated in the
> next merge window, that it be reviewed and that it be unit tested (i.e.
> tested as well as you can in isolation).  You seem to have done all that,
> so I will add it.
> 
> I will put it at the end of the merge today.
> 
> Andrew, does that make sense to you?

I'm not aware of any issues which would block a 2.6.27 merge.

I haven't reviewed the filesystem myself.  Christoph Hellwig seems to
have had a good go through it and had numerous review comments, but it
is unclear what stage things are at with addressing them?

  reply	other threads:[~2008-05-28  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  6:18 can UBIFS be taken to linux-next? Artem Bityutskiy
2008-05-28  1:41 ` Stephen Rothwell
2008-05-28  2:29   ` Andrew Morton [this message]
2008-05-28  5:03     ` Artem Bityutskiy
2008-05-28  5:14   ` Artem Bityutskiy

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=20080527192942.f4e3dd7b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=linux-kernel@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 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.