From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
Cc: sparclinux@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: SILO & Ext4
Date: Mon, 01 Jun 2009 03:41:24 -0700 (PDT) [thread overview]
Message-ID: <20090601.034124.38077655.davem@davemloft.net> (raw)
In-Reply-To: <a4423d670906010333x16cbae69g667a7441be2f140a@mail.gmail.com>
From: Alexander Beregalov <a.beregalov@gmail.com>
Date: Mon, 1 Jun 2009 14:33:02 +0400
> I found that Sparc cannot boot when rootfs is Ext4 (converted from ext3).
>
> Is anyone working on adding ext4 support to silo?
> Is it hard to implement?
I'm personally not going to work on this, that's for sure :-)
Although it shouldn't be hard.
All of my effort has been spent on adding sparc support to
grub2.
next prev parent reply other threads:[~2009-06-01 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:33 SILO & Ext4 Alexander Beregalov
2009-06-01 10:41 ` David Miller [this message]
2009-06-01 13:53 ` Alex Buell
2009-06-01 10:43 ` Alex Buell
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=20090601.034124.38077655.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).