Re: [PATCH 00/14] Blackfin on-chip SPI controller driver updates and bug-fixing

On 10/30/07, David Brownell <[email protected]> wrote:
> And also, pay closer attention to when you may be making
> changes that make device drivers work differently over
> your spi_master controller driver than anyone elses ...
> such platform-specific behaviors are undesirable, and when
> they go against specified behavior they are also bugs.

was there something that caught your eye other than the ugly udelay()
you mentioned in the other thread ?
-mike
-
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/

---

• Follow-Ups:
  • Re: [PATCH 00/14] Blackfin on-chip SPI controller driver updates and bug-fixing
    • From: David Brownell <[email protected]>

• References:
  • [PATCH 00/14] Blackfin on-chip SPI controller driver updates and bug-fixing
    • From: Bryan Wu <[email protected]>
  • Re: [PATCH 00/14] Blackfin on-chip SPI controller driver updates and bug-fixing
    • From: David Brownell <[email protected]>

• Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• Next by Date: [2.6 patch] fix drivers/net/wan/lmc/ compilation
• Previous by thread: Re: [PATCH 00/14] Blackfin on-chip SPI controller driver updates and bug-fixing
• Next by thread: Re: [PATCH 00/14] Blackfin on-chip SPI controller driver updates and bug-fixing
• 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]