to (politely) to support the case?
I don't understand your reluctance in this case (I do for your graphics
processors) - it's not as if adding this function to sata_nv would
expose your crown jewels - you write yourself that next time you'd use a
different (better) interface...
Re
id use it moved to os_scsi_tape_flush() recently.
James, could you make this change in BK too, please?
Signed-off-by: Willem Riede <[EMAIL PROTECTED]>
> --- linux-2.6.12-rc1-mm1-full/drivers/scsi/osst.c.old 2005-03-22
> 21:04:36.0 +0100
> +++ linux-2.6.12-rc1-mm1-full/d
On 03/22/2005 09:28:07 AM, Adrian Bunk wrote:
> This patch makes needlessly global code static.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
James, I agree with this, can you put it in BK, please?
Signed-off-by: Willem Riede <[EMAIL PROTECTED]>
> ---
>
>
* CONFIG_BLK_DEV_IDETAPE */
>
> Any reason for this to stay in the ide patch, or is it now obsolete?
>
It is obsolete, and can safely be removed.
Success. Willem Riede.
-
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/
Junfeng Yang wrote:
>
> On Thu, 24 May 2001, Willem Riede wrote:
>
> > Dawson Engler wrote:
> > >
> > > Hi All,
> > >
> > > Enclosed are 103 potential errors where code gets a pointer from a
> > > possibly-failing routine (kmalloc, etc
t; Error --->
> SRpnt->sr_sense_buffer[13] == 2) {
> printk(KERN_ERR "osst%d: Volume overflow in write
>error recovery\n", dev);
> vfree((void *)buffer);
>
es not try to support these drives and fails due to the drive
particulars. Since SCSI, USB and IDE versions of these drives exist,
patching st is more appropriate than ide-scsi.
Regards. Willem Riede.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
7 matches
Mail list logo
