linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: dougthompson@xmission.com, bp@alien8.de, m.chehab@samsung.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] edac: Remove fixmes in e7xxx_edac.c
Date: Tue, 22 Jul 2014 16:04:41 +0200	[thread overview]
Message-ID: <874my98p6u.fsf@nemi.mork.no> (raw)
In-Reply-To: <1406004789-9918-1-git-send-email-xerofoify@gmail.com> (Nicholas Krause's message of "Tue, 22 Jul 2014 00:53:09 -0400")

Nicholas Krause <xerofoify@gmail.com> writes:

> This removes two Page shift fixs me in this file and not checking
> if row is -1 in process_ce as it cannot be this value or be must
> exit this function by returning.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
>  drivers/edac/e7xxx_edac.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/edac/e7xxx_edac.c b/drivers/edac/e7xxx_edac.c
> index 3cda79b..563983f 100644
> --- a/drivers/edac/e7xxx_edac.c
> +++ b/drivers/edac/e7xxx_edac.c
> @@ -211,12 +211,13 @@ static void process_ce(struct mem_ctl_info *mci, struct e7xxx_error_info *info)
>  	edac_dbg(3, "\n");
>  	/* read the error address */
>  	error_1b = info->dram_celog_add;
> -	/* FIXME - should use PAGE_SHIFT */
> -	page = error_1b >> 6;	/* convert the address to 4k page */
> +	page = error_1b >> PAGE_SHIFT;	/* convert the address to 4k page */

I just have to bite...  Where did you get the idea that you can go
around and "fix" FIMXE's like they were spelling errors?


Bjørn

  reply	other threads:[~2014-07-22 14:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  4:53 [PATCH] edac: Remove fixmes in e7xxx_edac.c Nicholas Krause
2014-07-22 14:04 ` Bjørn Mork [this message]
2014-07-22 17:25   ` Tony Luck
2014-07-22 17:40     ` Nick Krause
2014-07-22 17:46       ` Borislav Petkov
2014-07-22 18:03         ` Nick Krause
2014-07-22 18:08           ` Borislav Petkov
2014-07-22 18:14       ` Levente Kurusa
2014-07-22 18:25         ` Nick Krause
2014-07-22 19:17           ` Randy Dunlap
2014-07-22 19:33           ` Steven Rostedt
2014-07-22 20:56             ` Nick Krause
2014-07-23 14:37               ` Steven Rostedt
2014-07-23 15:35                 ` Nick Krause
2014-07-23 16:07                   ` Steven Rostedt
2014-07-23 16:19                     ` Nick Krause

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=874my98p6u.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=bp@alien8.de \
    --cc=dougthompson@xmission.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=xerofoify@gmail.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 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).