All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RESENT PATCH 4/4] ocfs2: adjust switch_case syntax at o2net_state_change()
Date: Mon, 1 Jul 2013 17:57:44 -0700	[thread overview]
Message-ID: <20130702005743.GI965@localhost> (raw)
In-Reply-To: <20130701162228.e47209b0012101bab77b27ca@linux-foundation.org>

On Mon, Jul 01, 2013 at 04:22:28PM -0700, Andrew Morton wrote:
> On Mon, 1 Jul 2013 16:04:21 -0700 Joel Becker <jlbec@evilplan.org> wrote:
> 
> > On Sat, Jun 29, 2013 at 12:01:19PM +0800, Jeff Liu wrote:
> > > From: Jie Liu <jeff.liu@oracle.com>
> > > 
> > > Adjust switch..case syntax at o2net_state_change to meet
> > > the kernel coding standard.
> > > 
> > > s/printk/pr_info/.
> > > 
> > > Signed-off-by: Jie Liu <jeff.liu@oracle.com>
> > 
> > 	Switching to pr_info() hasn't been discussed as part of the
> > project.  Let's have that conversation elsewhere.
> > 
> 
> I reverted that bit.
> 
> It was wrong anyway:
> 
> > > +		pr_info(KERN_INFO "o2net: Connection to " SC_NODEF_FMT
> > > +			" shutdown, state %d\n",
> > > +			SC_NODEF_ARGS(sc), sk->sk_state);
> 
> Should remove the "KERN_INFO " now.
> 
> 
> Switching to pr_foo is a good idea, I find.  A nice thing about it is
> that it reduces the length of the lines quite a lot, and printk
> statements are often quite long lines.  The net effect is that a *lot*
> of nasty make-it-fit-in-80-columns tricks just vanish.

	That's good to know.

Joel

-- 

"Maybe the time has drawn the faces I recall.
 But things in this life change very slowly,
 If they ever change at all."

			http://www.jlbec.org/
			jlbec at evilplan.org

      reply	other threads:[~2013-07-02  0:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29  4:01 [Ocfs2-devel] [RESENT PATCH 4/4] ocfs2: adjust switch_case syntax at o2net_state_change() Jeff Liu
2013-07-01 23:04 ` Joel Becker
2013-07-01 23:22   ` Andrew Morton
2013-07-02  0:57     ` Joel Becker [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=20130702005743.GI965@localhost \
    --to=jlbec@evilplan.org \
    --cc=ocfs2-devel@oss.oracle.com \
    /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.