public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Arvind R <arvino55@gmail.com>
Cc: linux-edac <linux-edac@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.15.1] i82975x_edac: fix dram layout inits and style
Date: Fri, 20 Jun 2014 20:29:51 +0200	[thread overview]
Message-ID: <20140620182951.GH11391@pd.tnic> (raw)
In-Reply-To: <CAA_L+UPtA9ahtF4oeGCeR27e-q=tCtoKfXqDhrJR_UgVGu9Aaw@mail.gmail.com>

On Fri, Jun 20, 2014 at 09:26:27PM +0530, Arvind R wrote:
> Subject: [PATCH 3.15.1] i82975x_edac: fix dram layout inits and style
> 
> rewrite dram layout initialisation differently based on symmetry
> of organisation. And a long pending cleanup.

Yeah, this patch is trying to do a lot of things at once and could use some
splitting into single logical changes with proper explanations in their
respective commit messages *why* the changes are needed.

Also, do you test those changes on real hardware?

Also, you have some strange coding style like

+#define^II82975X_NR_CSROWS_PER_CHANNEL

 (there's a tab between the "define" and the name)

+^I^Iif (is_symmetric)^I{$

 (tab between closing bracket and opening curly brace)

and so on. Please use single spaces like the rest of the kernel code.

Use Documentation/CodingStyle as a guide.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

      reply	other threads:[~2014-06-20 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 15:56 [PATCH 3.15.1] i82975x_edac: fix dram layout inits and style Arvind R
2014-06-20 18:29 ` Borislav Petkov [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=20140620182951.GH11391@pd.tnic \
    --to=bp@alien8.de \
    --cc=arvino55@gmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.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