Martin, It looks like the numbers we picked for our respective IOCTLs conflict. I think I can change mine to the next higher since your patch seems to have been around longer. What is the general way to deal with these conflicts? -- Michael On 13 Feb 2001, Martin K. Petersen wrote: > >>>>> "Andries" == Andries Brouwer <[EMAIL PROTECTED]> writes: > > Andries> Anyway, an ioctl just to read the last sector is too silly. > Andries> An ioctl to change the blocksize is more reasonable. > > I actually sent you a patch implementing this some time ago, remember? > We need it for XFS... > > Patch against 2.4.2-pre3 follows. > > - 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/
- Re: block ioctl to read/write last sector Andries . Brouwer
- Re: block ioctl to read/write last sector Michael E Brown
- Re: block ioctl to read/write last sector Manfred Spraul
- Re: block ioctl to read/write last sector Michael E Brown
- Re: block ioctl to read/write last sector Martin K. Petersen
- Re: block ioctl to read/write last sector Michael E Brown
- Re: block ioctl to read/write last sector Martin K. Petersen
- Re: block ioctl to read/write last sector Andries . Brouwer
- Re: block ioctl to read/write last sector Michael E Brown
- RE: block ioctl to read/write last sector Matt_Domsch
- Re: block ioctl to read/write last sector David Balazic
- Re: block ioctl to read/write last sector Michael E Brown
- Re: block ioctl to read/write last sector Andre Hedrick
- RE: block ioctl to read/write last sector Matt_Domsch
- Re: block ioctl to read/write last sector Andries . Brouwer
- Re: block ioctl to read/write last sector Michael E Brown