public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
Cc: tglx@linutronix.de, hpa@zytor.com, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, UV: Support for SGI UV2 hub chip
Date: Tue, 10 May 2011 22:39:05 +0200	[thread overview]
Message-ID: <20110510203905.GD21903@elte.hu> (raw)
In-Reply-To: <20110510191110.GA18052@sgi.com>


* Jack Steiner <steiner@sgi.com> wrote:

> +				/*
> +				 * Our retries may be blocked by all destination
> +				 * swack resources being consumed, and a timeout
> +				 * pending.  In that case hardware returns the
> +				 * ERROR that looks like a destination timeout.
> +				 */
> +				if (cycles_2_us(ttime - bcp->send_message) <
> +								timeout_us) {
> +					bcp->conseccompletes = 0;
> +					return FLUSH_RETRY_PLUGGED;
> +				}

This code is sick. Symptom: too long lines. Illness: it's too complex.

checkpatch warned you but you applied the wrong cure: you only addressed the 
symptom and broke the lines in an ugly way.

You need to pick another cure. One of the many options:

  - eliminate many repetitive strings
  - reduce indentation by the introduction of helper inlines
  - sensible shortening of variable/field/definition names

... applies to this particular case and will solve the problem.

Note that there's other, similar incidents in this patch, please address all of 
them.

Thanks,

	Ingo

  reply	other threads:[~2011-05-10 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 19:11 [PATCH] x86, UV: Support for SGI UV2 hub chip Jack Steiner
2011-05-10 20:39 ` Ingo Molnar [this message]
2011-05-11 17:50   ` [PATCH V2] " Jack Steiner
2011-05-25 13:16     ` [tip:x86/urgent] x86, UV: Add support " tip-bot for Jack Steiner

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=20110510203905.GD21903@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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