On Wed, Aug 17, 2005 at 10:48:05PM -0700, Andrew Morton wrote:
> Pierre Ossman <[email protected]> wrote:
> >
> > >I'm thinking that it would be better to not have the config option there
> > >and then re-add it late in the 2.6.14 cycle if someone reports problems
> > >which cannot be fixed. Or at least make it default to 'y' so we get more
> > >testing coverage, then remove the config option later. Or something.
> > >
> > >Thoughts?
> > >
> > >
> >
> > Removing it would be preferable by me. All that #ifdef tends to clutter
> > up the code. After som initial problem with a buggy card everything has
> > worked flawlesly.
>
> OK.. Please send an additional patch for that sometime?
I'd rather not. The problem is that we have a host (thanks Intel)
which is unable to report how many bytes were transferred before an
error occurs. My fear is that doing anything other than sector by
sector write will lead to corruption should an error occur.
However, I've no way to induce such an error, so I can only base
this on theory.
It may work perfectly for the case when everything's operating
correctly, but I suspect if you're going to do multi-sector writes,
it'll all fall apart on the first error, especially on this host.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |