All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/5] usb:gadget:s5p USB Device Controller (UDC) implementation
Date: Mon, 10 Oct 2011 23:54:47 +0200	[thread overview]
Message-ID: <20111010215447.0E5291408777@gemini.denx.de> (raw)
In-Reply-To: <4E935BDC.7000109@freescale.com>

Dear Scott Wood,

In message <4E935BDC.7000109@freescale.com> you wrote:
>
> > Well, "user-visible strings" is definitely not the same thing as
> > "debug print code", at least not for me.
> 
> They're visible to a user that has #defined DEBUG.  They're something
> one might want to grep on.  checkpatch.pl explicitly considers

Strings yes. Code no.

> At some point you might want to consider actually writing down your
> interpretations of these things into a U-Boot coding style document, so
> at least we don't have to guess.

There is not much of interpretion.  Please stop discussing just for
the fun of it and switch on common sense.

This is bad:

			debug("This is a very, very long string just "
			      "to show what is meant by the CodingStyle "
			      "note about 'user-visible strings\n");
	
But this is bad, too:

				for (i = 0; i < 100; i++) {
					for (j = 0; j < 100; j++) {
						debug("f(i)=0x%08x, g(j)=0x%08x\n", some_function_doing_funny_things(i), some_other_function_doing_more_funny_things(j));
					}
				}

The first example is what the CodingStyle mentions: do not break
"user-visible strings".

The second example should clearly be reformatted, at least as:

				for (i = 0; i < 100; i++) {
					for (j = 0; j < 100; j++) {
						debug("f(i)=0x%08x, g(j)=0x%08x\n",
							some_function_doing_funny_things(i),
							some_other_function_doing_more_funny_things(j)
						);
					}
				}

or similar.

Agreed?

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@denx.de
"How is this place run - is it an anarchy?"
"No, I wouldn't say so; it is not that well organised..."

  reply	other threads:[~2011-10-10 21:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 14:29 [U-Boot] [PATCH v2 0/5] usb:gadget USB Gadget support Lukasz Majewski
2011-07-13 14:29 ` [U-Boot] [PATCH v2 1/5] usb:gadget:s5p USB Device Controller (UDC) implementation Lukasz Majewski
2011-07-13 14:43   ` Vitaly Kuzmichev
2011-07-14  8:14   ` [U-Boot] [RESEND PATCH " Lukasz Majewski
2011-10-06 22:10   ` [U-Boot] [PATCH " Wolfgang Denk
2011-10-07  7:39     ` Lukasz Majewski
2011-10-09 19:43       ` Wolfgang Denk
2011-10-10 20:00         ` Scott Wood
2011-10-10 20:38           ` Wolfgang Denk
2011-10-10 20:55             ` Scott Wood
2011-10-10 21:54               ` Wolfgang Denk [this message]
2011-10-10 22:00                 ` Scott Wood
2011-07-13 14:29 ` [U-Boot] [PATCH v2 2/5] usb:gadget:s5p Enabling the USB Gadget framework at GONI Lukasz Majewski
2011-07-13 14:29 ` [U-Boot] [PATCH v2 3/5] usb:gadget: USB Mass Storage - files from Linux kernel Lukasz Majewski
2011-10-06 22:10   ` Wolfgang Denk
2011-10-07  7:28     ` Lukasz Majewski
2011-10-07  8:25       ` Wolfgang Denk
2011-07-13 14:29 ` [U-Boot] [PATCH v2 4/5] usb:gadget: USB Mass Storage Gadget support Lukasz Majewski
2011-07-13 14:29 ` [U-Boot] [PATCH v2 5/5] usb:gadget:s5p Support for USB Mass Storage Gadget on GONI Lukasz Majewski

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=20111010215447.0E5291408777@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.