Re: [PATCH] [RFC] be more verbose when probing EDD

> Does printk support escape sequences? The last time I tried
> printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.

It should handle \r correctly. If not that is easy to fix.

Escape codes are bad and should not be used - you may have a serial
console and not be on a Linux console
--
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] [RFC] be more verbose when probing EDD
    • From: "H. Peter Anvin" <[email protected]>

• References:
  • Re: [PATCH] [RFC] be more verbose when probing EDD
    • From: [email protected]
  • Re: [PATCH] [RFC] be more verbose when probing EDD
    • From: "Parag Warudkar" <[email protected]>
  • Re: [PATCH] [RFC] be more verbose when probing EDD
    • From: Alan Cox <[email protected]>
  • Re: [PATCH] [RFC] be more verbose when probing EDD
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: [GIT PATCH] driver core and documentation fixes for 2.6.24-rc5
• Next by Date: Re: [PATCH] sysctl: Fix ax25 checks
• Previous by thread: Re: [PATCH] [RFC] be more verbose when probing EDD
• Next by thread: Re: [PATCH] [RFC] be more verbose when probing EDD
• 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]