All of lore.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Sancho Dauskardt <sda@bdit.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: FAT statfs loop abort on read-error
Date: Tue, 08 Jul 2003 23:46:11 +0900	[thread overview]
Message-ID: <87wuetnkjw.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <5.0.2.1.2.20030708142409.03e19c60@pop.kundenserver.de>

Sancho Dauskardt <sda@bdit.de> writes:

> >I don't know anybody ported dmsdos to 2.4. The cvf stuff was removed
> >and many error handlings was fixed on 2.5.x. So, personally I think to
> >remove the cvf stuff and backport the some parts of fat driver to 2.4
> >is good.
> 
> OK, the 100k diff between 2.4.21/fs/fat and 2.5.74 didn't really help
> me understand what's really changed (other than the cvf removal).
> Should I attempt to brute-force backport fs/fat/* in one large patch,
> or incrementally re-apply the 2.5 changes to 2.4 ?

I submited the some patch to marcelo several times about one year ago,
however, unfortunately those patches was ignored.

So, one large patch may not be applied. And incremental ways is more
safety, I think. (Probably, we need to address the difference of vfs
and umsdos)

> Or, as you write 'some parts', which parts would that be ?

I thought that the patches of only bug fix is probably easy to be
applied.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2003-07-08 14:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04 11:57 FAT statfs loop abort on read-error Sancho Dauskardt
2003-07-06 17:24 ` Randy.Dunlap
2003-07-07 15:54   ` OGAWA Hirofumi
2003-07-07 16:24     ` Christoph Hellwig
2003-07-08 12:18       ` OGAWA Hirofumi
2003-07-08 12:33         ` Christoph Hellwig
2003-07-08 14:56           ` OGAWA Hirofumi
2003-07-07 16:38     ` Jeff Garzik
2003-07-08 12:29     ` Sancho Dauskardt
2003-07-08 14:46       ` OGAWA Hirofumi [this message]
2003-09-11 20:47         ` Sancho Dauskardt
2003-09-12 17:12           ` OGAWA Hirofumi

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=87wuetnkjw.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=sda@bdit.de \
    /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.