Re: [PATCH] libata: Correct IORDY handling

> 
> > +			dev->pio_mode <= XFER_PIO_2)
> 
>     Overindented line (to my taste :-). And do we really need to check this?
> 

Yes - if it refuses SET_XFER_MODE we really don't want to run any mode
above PIO2. No hardware *should* do this but then this is IDE...
-
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/

---

• References:
  • [PATCH] libata: Correct IORDY handling
    • From: Alan Cox <[email protected]>
  • Re: [PATCH] libata: Correct IORDY handling
    • From: Sergei Shtylyov <[email protected]>

• Prev by Date: Re: [PATCH 0/2][RFC] VFCIPI v3
• Next by Date: Re: Time Problems with 2.6.23-rc1-gf695baf2
• Previous by thread: Re: [PATCH] libata: Correct IORDY handling
• Next by thread: Re: [PATCH] libata: Correct IORDY handling
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]