Date: Wed, 10 Jun 2009 20:49:55 -0700
From: Greg KH <gregkh@suse.de>
To: =?utf-8?B?VG9tw6HFoSBTesOpcGU=?= <szepe@pinerecords.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.28.x FIX] CONFIG_FILE_LOCKING should not depend on
	CONFIG_BLOCK
Message-ID: <20090611034954.GA21231@suse.de>
References: <20090611024019.GC25384@louise.pinerecords.com> <20090611024641.GA19767@suse.de> <20090611030759.GA25569@louise.pinerecords.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20090611030759.GA25569@louise.pinerecords.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 877
Lines: 22

On Thu, Jun 11, 2009 at 05:07:59AM +0200, Tomáš Szépe wrote:
> > > Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK.
> > > Patch against 2.6.28.10.
> > > 
> > > inlined please find a trivial fix that makes it possible to run
> > > complete systems out of an initramfs on 2.6.28.10 again (this
> > > broke somewhere between 2.6.27 and 2.6.28).
> > 
> > 2.6.28 is no longer supported, sorry.
> > Is this an issue in 2.6.29 or 2.6.30?
> 
> Yes.  I also sent a patch (in a separate email) that applies
> on 2.6.29.x, 2.6.30.x, and current git master branch head.

Ah, ok, I see that now, sorry for getting ahead.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/