linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>, Jan Mrazek <email@honzamrazek.cz>,
	"Theodore Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 1/1] Fix of coding style
Date: Mon, 26 Jan 2015 11:31:32 -0600	[thread overview]
Message-ID: <54C679F4.70306@redhat.com> (raw)
In-Reply-To: <54C67933.5050304@suse.cz>

On 1/26/15 11:28 AM, Jiri Slaby wrote:
> On 01/26/2015, 06:18 PM, Eric Sandeen wrote:
>> On 1/26/15 10:24 AM, Jan Mrazek wrote:
>>> - multiline strings changed to singleline (so it can be greped)
>>
>> Thereby blowing past 80 columns in many cases, something we generally
>> don't like to do, per Documentation/CodingStyle:
> 
> When you refer to that document, you certainly read the whole chapter 2 :).

OK, fair enough :)
 
>>> The limit on the length of lines is 80 columns and this is a strongly
>>> preferred limit.
>>
>> I'm not so sure about the grep-ability value, because nobody's going to
>> grep for "...%s): %s:%d: inode #%lu: ..." anyway...
> 
> Perhaps, but
>   grep EXT4.*block.*comm
> does the trick quite nice... And this is actually a nice example of the
> point of this exercise.
> 
>> but if it's really deemed desirable to keep these strings on one line,
>> we could do i.e.:
>>
>>> +			printk(KERN_CRIT
>>> +"EXT4-fs error (device %s): %s:%d: inode #%lu: block %llu: comm %s: %pV\n",
>>>  			       inode->i_sb->s_id, function, line, inode->i_ino,
>>>  			       block, current->comm, &vaf)
>>
>> which is a trick the xfs code uses in some places.
> 
> Oh no, that's ugly.

Eye of the beholder, etc.  ;)  Anyway, that's my $0.02, we can see what others
think.

-Eric


      reply	other threads:[~2015-01-26 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:24 [PATCH 1/1] Fix of coding style Jan Mrazek
2015-01-26 17:18 ` Eric Sandeen
2015-01-26 17:28   ` Jiri Slaby
2015-01-26 17:31     ` Eric Sandeen [this message]

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=54C679F4.70306@redhat.com \
    --to=sandeen@redhat.com \
    --cc=email@honzamrazek.cz \
    --cc=jslaby@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=trivial@kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).