From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] imls: Add support to list images in NAND device
Date: Fri, 14 Dec 2012 12:59:36 -0600 [thread overview]
Message-ID: <1355511576.4740.5@snotra> (raw)
In-Reply-To: <50CAF00E.90403@st.com> (from vipin.kumar@st.com on Fri Dec 14 03:23:26 2012)
On 12/14/2012 03:23:26 AM, Vipin Kumar wrote:
> On 12/14/2012 3:22 AM, Scott Wood wrote:
>> On 12/13/2012 12:10:58 AM, Vipin Kumar wrote:
>>>>> + imgdata = malloc(read_size);
>>>>> + if (!imgdata) {
>>>>> + printf("Not able to list all
>>>>> images " \
>>>>> + "(Low memory)\n");
>>>>
>>>> Don't line-wrap error strings.
>>>>
>>>
>>> 80 column ?
>>
>> Error strings are an exception for the sake of greppability. From
>> Linux's Documentation/CodingStyle:
>>
>> Statements longer than 80 columns will be broken into sensible
>> chunks, unless
>> exceeding 80 columns significantly increases readability and does
>> not hide
>> information. Descendants are always substantially shorter than
>> the
>> parent and
>> are placed substantially to the right. The same applies to
>> function
>> headers
>> with a long argument list. However, never break user-visible
>> strings
>> such as
>> printk messages, because that breaks the ability to grep for
>> them.
>>
>
> Yes, thanks for reminding. The error strings are more readable
> already in v3. Please take a look
No, you're still breaking up strings (and you also have a totally
unnecessary backslash). If it's on one line in the output, it should
be on one line in the source.
-Scott
next prev parent reply other threads:[~2012-12-14 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 9:20 [U-Boot] [PATCH v2] imls: Add support to list images in NAND device Vipin Kumar
2012-12-12 20:24 ` Wolfgang Denk
2012-12-13 5:51 ` Vipin Kumar
2012-12-12 23:00 ` Scott Wood
2012-12-13 6:10 ` Vipin Kumar
2012-12-13 21:52 ` Scott Wood
2012-12-14 9:23 ` Vipin Kumar
2012-12-14 18:59 ` Scott Wood [this message]
2012-12-17 8:18 ` Vipin Kumar
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=1355511576.4740.5@snotra \
--to=scottwood@freescale.com \
--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