public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2] x86: UV BAU fix for non-consecutive nasids
Date: Wed, 11 May 2011 09:25:00 +0200	[thread overview]
Message-ID: <20110511072500.GJ22551@elte.hu> (raw)
In-Reply-To: <E1QJmxX-0002Mz-Fk@eag09.americas.sgi.com>


* Cliff Wickman <cpw@sgi.com> wrote:

> From: Cliff Wickman <cpw@sgi.com>
> 
> (patch v2 has improved changelog and correction of a broken line)

but i did not point out just a single broken line - there's literally a dozen 
in your patch, still!

*All* of these measures i mentioned in my previous mail:

  - 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.

This whole file is still utterly ugly and i'm not surprised at all it's showing 
bugs. Functions are still *way* too large and the code is hard to read.

If you don't know how to simplify a particular function then please ask but i 
see half a dozen things that could be done to clean up any of these big 
functions, just at a first quick glance. Those patterns of code ugliness repeat 
all over the whole file!

I dont mind if you do it as delta patches after this fix (so that the fix stays 
mergable) but we need to see progress in this code first, the pain in this file 
has been going on for *way* too long.

Thanks,

	Ingo

  reply	other threads:[~2011-05-11 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 13:26 [PATCH v2] x86: UV BAU fix for non-consecutive nasids Cliff Wickman
2011-05-11  7:25 ` Ingo Molnar [this message]
2011-05-13  6:52 ` [tip:x86/urgent] x86: Fix UV BAU " tip-bot for Cliff Wickman

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=20110511072500.GJ22551@elte.hu \
    --to=mingo@elte.hu \
    --cc=cpw@sgi.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.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