From: "Tomáš Szépe" <szepe@pinerecords.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.28.x FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK
Date: Thu, 11 Jun 2009 05:07:59 +0200 [thread overview]
Message-ID: <20090611030759.GA25569@louise.pinerecords.com> (raw)
In-Reply-To: <20090611024641.GA19767@suse.de>
> > 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.
Best regards,
--
Tomáš Szépe <szepe@pinerecords.com>
next prev parent reply other threads:[~2009-06-11 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 2:40 [2.6.28.x FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK Tomáš Szépe
2009-06-11 2:46 ` Greg KH
2009-06-11 3:07 ` Tomáš Szépe [this message]
2009-06-11 3:49 ` Greg KH
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=20090611030759.GA25569@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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