From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Incorrect escape sequences in u-boot-1.3.3/common/usb.c
Date: Tue, 20 May 2008 11:29:23 +0200 [thread overview]
Message-ID: <20080520092923.50ED2247A5@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 20 May 2008 02:16:36 PDT." <17336362.post@talk.nabble.com>
Dear Gururaja,
in message <17336362.post@talk.nabble.com> you wrote:
>
> While going through some the files that i use for my u-boot version, i found
> an incorrect escape sequence mentioned in u-boot-1.3.3/common/usb.c. Below
> is the patch that corrects the same.
Thanks. Had to apply manually, as your patch is line-wrapped.
> Here in my company i cannot use git and hence no git-patch or git-mail.
> sorry for that..
What could you prevent from using git? I cannot imagine...
> - USB_HUB_PRINTF("usb_hub_configure: failed to get hub descriptor - too
> long: %d\N",
^^^^^^^^^^^^^^^^^^
> + USB_HUB_PRINTF("usb_hub_configure: failed to get hub descriptor - too
> long: %d\n",
^^^^^^^^^^^^^^^^^^
Please fix your mailer to not wrap lines!
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Do not underestimate the value of print statements for debugging.
Don't have aesthetic convulsions when using them, either.
next prev parent reply other threads:[~2008-05-20 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 9:16 [U-Boot-Users] [PATCH] Incorrect escape sequences in u-boot-1.3.3/common/usb.c Hebbar
2008-05-20 9:29 ` Wolfgang Denk [this message]
2008-05-20 9:34 ` Hebbar
2008-05-20 12:26 ` Wolfgang Denk
2008-05-20 15:38 ` Jean-Christophe PLAGNIOL-VILLARD
2008-05-20 20:21 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080520092923.50ED2247A5@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox